hi, Fred
thanks for the thoughts. my opinion please see following inlined response.
IMHO, the most important thing we have to consider is the stable of this system. if we have eyes on the resources usage, it should be good enough to open it.
let's discuss it on today's meeting.
Hi Infrastructure team,
From last weekly meeting[1] I took one action “fred_li get the schedule of open OBS”.
The following needs to be analyzed and assessed:
1. Volume. About how many engineers does it support?
[freesky-edward] first stage, we can provide the resourse useage report and give a extension mechenisim.
2. Elastic resource support or not: if access exceeds the criteria, will it restrict, or trigger elastic resource?
[freesky-edward] it is very hard to answer this question now, but we can open it and have a try with fully usage monitor.
3. account management:
[freesky-edward] already exists.
4. domain name or IP we will use.
[freesky-edward] I am researching in this question, the initial option will be
openeuler.org via proxy.
5. anything else we have got from uses(like OVS)?
If infrastructure team can provide feedback by Feb 7th, that will be fantastic.
[1] http://meetings.openeuler.org/openeuler-meeting/2020/infrastructure/2020-01-21-09.00.html
Fred 李永乐
_______________________________________________
Infra mailing list -- infra@openeuler.org
To unsubscribe send an email to infra-leave@openeuler.org