From corvus at inaugust.com Mon Feb 4 19:04:34 2019 From: corvus at inaugust.com (James E. Blair) Date: Mon, 04 Feb 2019 11:04:34 -0800 Subject: [OpenStack-Infra] Gitea next steps Message-ID: <871s4n8jel.fsf@meyer.lemoncheese.net> Hi, At the last infra team meeting, we talked about whether and how to proceed with Gitea. I'd like to summarize that quickly and make sure we're all on board with it. * We will continue to deploy our own Kubernetes using the k8s-for-openstack Ansible playbook that Monty found. Since that's developed by a third-party, we will use it by checking out the upstream source from GitHub, but pinning to a known sha so that we don't encounter surprises. * We discussed deploying with a new version of rook which does not require the flex driver, but it turns out I was a bit ahead of things -- that hasn't landed yet. So we can probably keep our current deployment. Ian raised two new issues: 1) We should verify that the system still functions if our single-master Kubernetes loses its master. Monty and I tried this -- it doesn't. The main culprit here seems to be DNS. The single master is responsible for intra-(and extra!)-cluster DNS. This makes gitea unhappy for three reasons: a) if its SQL connections have gone idle and terminated, it cannot re-establish them, and b) it is unable to resolve remote hostnames for avatars, which can greatly slow down page loads, and c) the replication receiver is not a long running process, it's just run over SSH, so it can't connect to the database either, and therefore replication fails. The obvious solution, use a multi-master setup, apparently has issues if k8s is deployed in a cloud with LoadBalancer objects (which we are using). Kubernetes does have support for scale-out DNS, it's not clear whether that still has a SPOF though. Monty is experimenting with this. If that doesn't improve things, we may still want to proceed since the system should still mostly work for browsing and git clones if the master fails, and full operation will resume when it comes online. 2) Rook is difficult to upgrade. This appears to be the case. When it does come time to upgrade rook, we may want to simply build a new Kubernetes cluster for the system. Presumably by that point, it won't require the flexvolume driver, which will be a good reason to make a new cluster anyway, and perhaps further upgrades after that won't be as complicated. Once we conclude investigation into issue #1, I think these are the next steps: * Land the patches to manage the opendev k8s cluster with Ansible. * Pin the k8s-on-openstack repo to the current sha. * Add HTTPS termination to the cluster. * Update opendev.org DNS to point to the cluster. * Treat this as a soft-launch of the production service. Do not publicise it or encourage people to switch to it yet, but continue to observe it as we complete the rest of the tasks in [1]. [1] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.html#work-items -Jim From fungi at yuggoth.org Mon Feb 4 19:23:54 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 4 Feb 2019 19:23:54 +0000 Subject: [OpenStack-Infra] Gitea next steps In-Reply-To: <871s4n8jel.fsf@meyer.lemoncheese.net> References: <871s4n8jel.fsf@meyer.lemoncheese.net> Message-ID: <20190204192354.f4dayryblq3d53r2@yuggoth.org> On 2019-02-04 11:04:34 -0800 (-0800), James E. Blair wrote: [...] > I think these are the next steps: > > * Land the patches to manage the opendev k8s cluster with Ansible. > > * Pin the k8s-on-openstack repo to the current sha. > > * Add HTTPS termination to the cluster. > > * Update opendev.org DNS to point to the cluster. > > * Treat this as a soft-launch of the production service. Do not > publicise it or encourage people to switch to it yet, but continue to > observe it as we complete the rest of the tasks in [the spec] [...] I must confess having not been around much for the last two weeks so am still catching up, but this sounds good to me. Thanks for the careful planning! -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From cboylan at sapwetik.org Thu Feb 7 18:29:26 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 07 Feb 2019 10:29:26 -0800 Subject: [OpenStack-Infra] Contribution as Infrastructure Support. In-Reply-To: References: Message-ID: <1549564166.2545184.1653104160.50631B49@webmail.messagingengine.com> On Thu, Jan 31, 2019, at 12:20 PM, Javier Romero wrote: > Hi Team, > My name is Javier and live in Buenos Aires, Argentina. > > Work in the Network Operations Center of an Internet Service Provider where > I deploy and manage mission critical Linux Servers. > > Would like to know, if there is something I can help with on the OpenStack > Infrastructure Team. > > Thanks for your attention. Sorry for the slow response, I have been traveling recently. We are always happy to have contributions/help to run the development infastructure for OpenStack. Currently our big efforts are around modernizing our configuration management [0] and updating our git hosting setup [1]. One place to start may be with reviewing changes that implement these efforts [2]. Other tasks that we have in progress are updating our older servers to Xenial or Bionic from Precise [3]. We will also likely need to do some Gerrit plugin work in the near future to improve our ability to create and rename projects as well as restart Gerrit without pushing all replicated repos. This work will likely involve a lot of Java. If any of this sounds interesting to you let me know and I can help walk you through it a bit more (feel free to contact me directly via email or IRC (freenode #openstack-infra, my nick is clarkb) as you get bootstrapped as well). If this doesn't look interesting but you would still like to get involved feel free to share you interests and we may be able to find some good fits for them. Finally, our user [4] and administrator [5] docs are a good place to read through to get a sense for how we operate and how our users use our services. [0] http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html [1] http://specs.openstack.org/openstack-infra/infra-specs/specs/opendev-gerrit.html [2] https://review.openstack.org/#/q/status:open+AND+(topic:update-cfg-mgmt+OR+topic:puppet-4+OR+topic:opendev-gerrit) [3] https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup [4] https://docs.openstack.org/infra/manual/ [5] https://docs.openstack.org/infra/system-config/ Hope this helps, Clark From fungi at yuggoth.org Thu Feb 7 22:07:22 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 7 Feb 2019 22:07:22 +0000 Subject: [OpenStack-Infra] Contribution as Infrastructure Support. In-Reply-To: <1549564166.2545184.1653104160.50631B49@webmail.messagingengine.com> References: <1549564166.2545184.1653104160.50631B49@webmail.messagingengine.com> Message-ID: <20190207220721.hfox2hsuejnrojik@yuggoth.org> On 2019-02-07 10:29:26 -0800 (-0800), Clark Boylan wrote: [...] > updating our older servers to Xenial or Bionic from Precise [...] Not to be pedantic, but hopefully we haven't had any servers running Ubuntu Precise for a while now. We are still working to replace most of the ones running Ubuntu Trusty however, as it will be EOL soon. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From cboylan at sapwetik.org Thu Feb 7 22:51:54 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 07 Feb 2019 14:51:54 -0800 Subject: [OpenStack-Infra] OpenDev logo Message-ID: <1549579914.3318397.1653276328.7DC24977@webmail.messagingengine.com> Hello everyone, As the Gerrit hosting (gitea) spec [0] gets closer and closer to running in production as a preview site we suddenly have more of a need for establishing the opendevyness of the site. During the name selection one of the benefits of "opendev" was that the foundation had already done branding and logo work for the name in its use with the conferences in prior years. James was kind enough to put together a quick pdf of the current logo and what it might look like on a couple of our existing sites (see [0]). I'm throwing this out here so we can take a quick look at it. If there aren't objections to moving forward with this existing set of artifacts I'll work with James to get a set of reusable files for things like gitea. [0] https://tarballs.openstack.org/ci/OpenDev_Examples.pdf Clark From ssbarnea at redhat.com Fri Feb 8 07:22:16 2019 From: ssbarnea at redhat.com (Sorin Sbarnea) Date: Fri, 8 Feb 2019 07:22:16 +0000 Subject: [OpenStack-Infra] OpenDev logo In-Reply-To: <1549579914.3318397.1653276328.7DC24977@webmail.messagingengine.com> References: <1549579914.3318397.1653276328.7DC24977@webmail.messagingengine.com> Message-ID: I do like the logo and I am sure it look really cool in print. At the same time I find it not simple enough for use as a (fav)icon — where it will likely render like a pink dot. Remember times where this meant 16x16? :) Too many lines and too thin to make it recognisable at small sizes (even with retina displays). Maybe we could have a special low-detail version that is appropriate for this use case? -- sorin > On 7 Feb 2019, at 22:51, Clark Boylan wrote: > > Hello everyone, > > As the Gerrit hosting (gitea) spec [0] gets closer and closer to running in production as a preview site we suddenly have more of a need for establishing the opendevyness of the site. During the name selection one of the benefits of "opendev" was that the foundation had already done branding and logo work for the name in its use with the conferences in prior years. James was kind enough to put together a quick pdf of the current logo and what it might look like on a couple of our existing sites (see [0]). > > I'm throwing this out here so we can take a quick look at it. If there aren't objections to moving forward with this existing set of artifacts I'll work with James to get a set of reusable files for things like gitea. > > [0] https://tarballs.openstack.org/ci/OpenDev_Examples.pdf > > Clark > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra From cboylan at sapwetik.org Fri Feb 8 21:56:17 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 08 Feb 2019 13:56:17 -0800 Subject: [OpenStack-Infra] OpenDev logo In-Reply-To: References: <1549579914.3318397.1653276328.7DC24977@webmail.messagingengine.com> Message-ID: <1549662977.1707089.1654015736.1C737C67@webmail.messagingengine.com> On Thu, Feb 7, 2019, at 11:22 PM, Sorin Sbarnea wrote: > I do like the logo and I am sure it look really cool in print. > > At the same time I find it not simple enough for use as a (fav)icon — > where it will likely render like a pink dot. Remember times where this > meant 16x16? :) > > Too many lines and too thin to make it recognisable at small sizes (even > with retina displays). > > Maybe we could have a special low-detail version that is appropriate for > this use case? I've attached a current 32x32 favicon. I expect that we could use some other version for these small sizes if necessary too. Clark -------------- next part -------------- A non-text attachment was scrubbed... Name: opendev_32x32.png Type: image/png Size: 2398 bytes Desc: not available URL: From cboylan at sapwetik.org Mon Feb 11 19:03:21 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 11 Feb 2019 11:03:21 -0800 Subject: [OpenStack-Infra] OpenStack Infra Meeting February 12, 2019 Agenda Message-ID: <1549911801.858077.1655751456.6A5C27EB@webmail.messagingengine.com> If you get a moment between now and the meeting please review the LetEncrypt spec (linked below) so that we can have a productive discussion around that. == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval ** [https://review.openstack.org/#/c/587283/ LetsEncrypt Spec] Need to find agreement on path forward for this so we can more easily https all the things. * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:puppet-4 and topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev * General topics ** PTG planning for Denver, May 2-4 (clarkb 20190212) ** https://etherpad.openstack.org/2019-denver-ptg-infra-planning ** Running zuul-preview for netlify site previews (corvus 20190212) * Open discussion From fungi at yuggoth.org Wed Feb 13 14:54:28 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 13 Feb 2019 14:54:28 +0000 Subject: [OpenStack-Infra] [infra] StoryBoard Maintenance 2019-02-15 at 20:00 UTC Message-ID: <20190213145427.64uuaxb5i3cjtyy7@yuggoth.org> We're planning to perform a quick server upgrade/replacement and database move for the StoryBoard service at https://storyboard.openstack.org/ this Friday, 2019-02-15 starting at 20:00 UTC and hopefully only lasting 5-10 minutes. Please find us in the #openstack-infra channel on the Freenode IRC network or follow up to this message if you have any questions or concerns. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From cboylan at sapwetik.org Mon Feb 18 19:15:21 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 18 Feb 2019 14:15:21 -0500 Subject: [OpenStack-Infra] Infra Meeting Agenda for February 19, 2019 Message-ID: <5886b40d-1a6d-44d3-9cbe-770008264803@www.fastmail.com> See you all tomorrow to talk about: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval ** [https://review.openstack.org/#/c/587283/ LetsEncrypt Spec] New updates with DNS based validation. * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:puppet-4 and topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev *** Gitea updates (clarkb 20190219) * General topics ** Handling gpg-agent/emacs better on bridge (frickler 20190914) ** Trusty server upgrade progress (clarkb 20190219) *** https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup * Open discussion From kor.jmlim at gmail.com Wed Feb 20 08:37:18 2019 From: kor.jmlim at gmail.com (Jea-Min Lim) Date: Wed, 20 Feb 2019 17:37:18 +0900 Subject: [OpenStack-Infra] requesting update gerrit group member for ku.stella Message-ID: Dear infra-team, Last year, I commit ku.stella and I think the initial import has been finished. (https://review.openstack.org/#/c/623396/) Please add me as the Gerrit group member for ku.stella. If I missed something, reply to me plz. Regrets, Jea-Min Lim -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Wed Feb 20 15:04:56 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 20 Feb 2019 15:04:56 +0000 Subject: [OpenStack-Infra] requesting update gerrit group member for ku.stella In-Reply-To: References: Message-ID: <20190220150456.g6kxlv2zdnhjxmv4@yuggoth.org> On 2019-02-20 17:37:18 +0900 (+0900), Jea-Min Lim wrote: > Last year, I commit ku.stella and I think the initial import has been > finished. > (https://review.openstack.org/#/c/623396/) > > Please add me as the Gerrit group member for ku.stella. > If I missed something, reply to me plz. I have added your Gerrit account as the initial member of https://review.openstack.org/#/admin/groups/ku.stella-core and so you should now be able to add and remove any other members as needed. Let us know if you need anything else! -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From 195446040 at qq.com Thu Feb 21 08:49:30 2019 From: 195446040 at qq.com (=?gb18030?B?0Me54g==?=) Date: Thu, 21 Feb 2019 16:49:30 +0800 Subject: [OpenStack-Infra] can i Join the openstack.slack.com Message-ID: hi: my name is mark,i want to join openstack.slack.com,my email is 195446040 at qq. can the admin invite me.thanks a lot. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Feb 21 17:17:24 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 21 Feb 2019 17:17:24 +0000 Subject: [OpenStack-Infra] can i Join the openstack.slack.com In-Reply-To: References: Message-ID: <20190221171724.vulmcac6goo35xgy@yuggoth.org> On 2019-02-21 16:49:30 +0800 (+0800), 星光 wrote: > my name is mark,i want to join openstack.slack.com,my email is > 195446040 at qq. can the admin invite me.thanks a lot. The OpenStack community does not use Slack for its discussions. I recommend either IRC, mailing lists or the ask service we maintain. Information on these can be found in our Users’ Contributor Guide here: https://docs.openstack.org/contributors/users/index.html I don't know much about Slack, but some colleagues have informed me the openstack.slack.com you found is not officially associated with the OpenStack community and is operated by a company named "Cloudify" but beyond that I have no other information about it. I've also heard from people who tried to monitor it at one time that it's basically just full of users asking confused questions and getting no answers. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From cboylan at sapwetik.org Mon Feb 25 19:11:34 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 25 Feb 2019 14:11:34 -0500 Subject: [OpenStack-Infra] Infra Team Meeting Agenda for February 26, 2019 Message-ID: <9ddf2466-f09a-49be-9d78-d2f1b271d80f@www.fastmail.com> == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval ** [https://review.openstack.org/#/c/587283/ LetsEncrypt Spec] * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:puppet-4 and topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev * General topics ** Trusty server upgrade progress (clarkb 20190226) *** https://etherpad.openstack.org/p/201808-infra-server-upgrades-and-cleanup ** Infra/OpenDev Update and/or Onboarding sessions at the Denver summit (clarkb 20190226) * Open discussion From cboylan at sapwetik.org Wed Feb 27 00:07:55 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 26 Feb 2019 19:07:55 -0500 Subject: [OpenStack-Infra] Virtual Sprint for Server Upgrades Message-ID: <396313f6-1bf3-4c69-a428-cc6a52b02c41@www.fastmail.com> Hello everyone, As mentioned in today's meeting I would propose some days for a sprint to update some of the last remaining Trusty servers we've got that need host upgrades. I've talked to the OpenStack release team and their opinion was that potentially impactful upgrades prior to RC1 would be better than after RC1. Given that feedback I think either March 11 and 12 or March 14 and 15 are going to be our best bets. Maybe March 7 and 8, but that set of days is much closer to the present than the other two sets. Do we have a preference for any of these groups of days? I think if I had my pick I would go for the 11th and 12th simply because it gives us a slightly bigger buffer to the RC1 week (the week after). Clark