09:00:41 #startmeeting infrastructure 09:00:41 Meeting started Tue Feb 4 09:00:41 2020 UTC and is due to finish in 60 minutes. The chair is freesky-edward. Information about MeetBot at https://openeuler.org/en/meetings.html. 09:00:41 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 09:00:41 The meeting name has been set to 'infrastructure' 09:01:25 it seems not many topics 09:01:27 https://gitee.com/openeuler/infrastructure/wikis/Meeting%20Schedule 09:01:40 #topic open OBS 09:02:16 fred is not here 09:02:36 tommylikehu just check whether is it ready to open the OBS? what should we consider? 09:02:40 i think he do concern this topic 09:02:51 I saw the mail about opening OBS sent by tommylikehu 09:03:13 imjoey what's your opinion? 09:03:39 yeah, it's only about open this website to the public, I think there is no big difference with the jenkins website 09:03:51 it's/if it's 09:04:31 IMO, opening OBS is great. And we could do enough preparations but cannot all. We could go with it. 09:04:47 Solve the problem when it occurs. 09:05:00 tommylikehu which domain do you think is going to locate? 09:05:11 imjoey totally agree 09:05:14 agreed with tommylikehu . Nothing different with opening Jenkins server. 09:05:19 @freesky-edward we need someone who familiar with current developing process to write the document 09:05:53 tommylikehu that's a good option we'd list. 09:05:55 freesky-edward: domain ? we can have domain now? 09:06:46 openeuler.org 09:06:59 How about build.openeuler.org or obs.openeuler.org ? 09:07:26 ok 09:07:37 prefer build.openeuler.org 09:07:42 imjoey xxx.openeuler.org cannot work as the ICP approval 09:07:50 sorry, just login 09:07:57 fred_li hi 09:08:07 freesky-edward: oh, sorry for that 09:08:11 hi all, please continue. I will catch you up 09:08:25 I am going to use openeuler.org/build 09:08:30 fred_li: finally you here 09:08:45 fred_li: good to see you 09:09:09 freesky-edward: A good choice. 09:09:21 tommylikehu, if it is possible to change current deployment with `build` as the app name? 09:09:31 imjoey tommylikehu hi friends 09:10:00 freesky-edward: what the deployment 09:10:14 you mean the deployment file? 09:10:37 I mean use `http:///build` as the OBS app deployment link? 09:11:28 currently, we use the / as the OBS uri. can we change it into `/build` 09:11:48 if so, we can proxy the link with openeuler.org/build 09:13:04 yeah, it's configurable 09:13:12 how many IP addresses will be there? Does it impact the solution? 09:13:18 good news, tommylikehu 09:13:45 although I can't understand whether change the url path can help fixing this issue. 09:14:00 what's the impact do you think if we change the OBS root link? 09:14:04 fred_li back please! 09:15:05 freesky-edward: not sure, may have issues when jump internally. 09:15:41 it's all depends on whether the oba website has compatible logic. 09:16:14 if so, please hold on, let me have a try whether is it possible to proxy with / link 09:16:34 sure 09:17:38 what's your opinion on the resource monitor and privilege control? 09:18:29 we already has everything monitored so far 09:18:54 I don't have any idea on privileged control 09:19:12 or whether we need provileged control 09:19:45 imjoey are you fimiliar with OBS? 09:20:01 it would be better if could connect the users between OBS and gitee. 09:20:36 freesky-edward: no, sorry. Our team is still learning about it. We are using koji internally. 09:21:06 imjoey great thoughts 09:21:16 koji? fedora guys 09:22:04 it looks it would be better if we can do the CLA check before register OBS account 09:22:06 tommylikehu: well, all is about legacy. 09:23:09 freesky-edward: what's the point 09:24:11 CLA checking before OBS registration may require changes on the OBS itself ? I guess that's not easy. 09:24:12 I throw it out as I am thinking if is it possible to contribute code via OBS directly? 09:24:40 imjoey: I think from current developing design, the obs is not visible for end users. they could only notice that the jenkins is using osc to build and validate the package 09:25:31 freesky-edward: that would be a very biiiiiiiiiiiiiiiiiiiiiiiiiig changes. 09:26:02 tommylikehu according to your idea, there is no case to open OBS. am I right? 09:27:21 we need, at least let the user know there is an OBS system inside and how to visit it. 09:28:21 tommylikehu, do they allow to register account? 09:28:29 yeah 09:28:33 anyone can 09:28:42 contribution? 09:28:46 tommylikehu: you mean only authorized users could be able to use it, others can only access ? 09:28:52 does it allow to? 09:29:18 freesky-edward: they can't contribute the code on OBS directly. 09:29:50 they can fork the package and debug in their home project. and them submit codes via gitee. 09:30:33 imjoey: the role management is not open now, that is to say, any one can register obs system with read access. 09:30:35 the system open the way to contribute, but we don't accept them, am I right? 09:31:39 freesky-edward: yeah, maybe our maintainers are not familiar with how to corporate on obs system either. (I guess) 09:33:26 that's fine, if so, can we make the conclusion that the only two things should be done are 1. research the account management. 2. integration OBS with openeuler.org domain, right? 09:34:08 it will be ready when the above two finished. 09:34:26 two options 09:34:49 ok 09:35:13 yep, It seems that gitee is the only system that contributors should concern, OBS is a dashboard to see the building and validating. am i right ? 09:35:30 imjoey: have you ever tried to contribute any openeuler packages on gitee? 09:36:35 I am wondering what's the big diadvantage you think of considering the whole developing process. 09:36:36 imjoey if i am correct, OBS is not only the dashboard but the tool to compile package locally. 09:37:26 tommylikehu that's the same thing wonder me much. 09:37:44 Not yet, our team and I are already prepared to make contribution to some packages. 09:38:16 imjoey do you know the way to build package now? 09:38:19 freesky-edward: yeah this is another reason why we need open obs, otherwise developers would have no way to debug locally. 09:38:44 tommylikehu agree 09:39:02 from my perspective, currently we cannot validate our patch. 09:39:58 but, from the infrastructure team, we'd consider how to know whether the resources is enough to do taht. 09:40:11 If OBS could support compile locally, that will really great. 09:40:28 imjoey: may I ask you try to contribute in openeuler packages and give us the feedback on the issues? 09:40:37 imjoey, I think so if I understand correctly. 09:40:54 something unfriendly or inconveniently 09:42:08 that would be much helpful to us if someone know the work process. 09:42:38 tommylikehu: sure, my pleasure. I'll post issues about them. 09:43:18 imjoey thanks 09:44:05 yep, I could get some points from what we are doing with koji for product release. 09:44:08 regarding to the two options. tommylikehu , could you please help on #1 research the role management? 09:44:18 sure 09:44:34 I would like to take another one. 09:44:46 tommylikehu thanks 09:45:04 freesky-edward: to be exactly. what's the goal for action one? 09:46:10 in my opinion, we'd know how many users are using it and how much resource taken. 09:47:10 we'd better know the time when to add the worker 09:48:24 that could be done via adding alerting rule on alert manager 09:48:54 tommylikehu, that's another good way 09:49:38 if we know how to manage the users, it would be better. 09:49:54 sure 09:50:10 ok, let's move to next 09:50:19 #topic open discussion 09:50:55 I've two for discussion. :-) 09:51:06 please imjoey 09:51:46 1st is that will jenkins also have a similar domain, instead of ip address? 09:52:26 imjoey, good question. 09:53:21 yeah! 09:53:24 currently, I am afraid it desn't have chance to finish as the same reason of ICP application 09:53:38 :-) that will be equal to OBS, I guess. 09:54:09 yeah, let me try to find way to proxy it 09:54:29 quite annoying 09:54:30 how about openeuler.org/ci, or any uri, like the domain for OBS ? 09:55:01 I think it be 09:55:11 any option oks to me only it's a domian 09:55:19 yep, ip address is rather difficult to remember. 09:55:35 imjoey agree 09:56:09 that's could be called a life saver. ;) 09:56:23 we also has the issue with out grafana website 09:56:40 #action freesky-edward find way to set the jenkins domain 09:56:51 what's the IP address. freesky-edward you asked one hour ago 09:57:27 tommylikehu OBS address? 09:58:00 no grafana address. 09:58:00 imjoey not much time left, how about your next one? 09:58:39 sorry, I cannot remember it now :( 09:58:47 ok, it's about the action for me to add support renaming repositories. 09:59:14 imjoey fine 09:59:15 freesky-edward: http://119.8.45.72:3000/ 09:59:35 imojey could you please #action it? 09:59:47 Gitee OpenAPI only support rename the name of repository but its path, which is used for git clone command. 09:59:49 tommylikehu thanks 10:00:21 imjoey great improvement. 10:00:25 I've posted an issue to Gitee officials to ask for supports five days ago, no response yet. 10:01:06 imjoey could you please send link to me 10:01:14 So I'm afraid that that action will delay until Gitee OpenAPI support it. 10:01:16 they are on holiday 10:01:21 I will have a look at it 10:01:29 https://gitee.com/oschina/git-osc/issues/I18R3F 10:02:02 imjoey, got it , thanks 10:02:03 I also open an issue at openeuler/ci-bot for tracing that. 10:02:32 time is out 10:02:46 I am afraid I have to close the meeting. 10:03:03 anything else let's go on next time 10:03:05 okey, we could take more in our IRC channel if needed. 10:03:06 thanks all 10:03:08 we can discuss on @openeuler-infra 10:03:12 if needed 10:03:16 thanks 10:03:19 imjoey +1 10:03:20 ok, thank you all . 10:03:29 88 10:03:32 #endmeeting