From mohibbillah10 at gmail.com Thu Apr 2 05:44:12 2020 From: mohibbillah10 at gmail.com (mohibtech) Date: Thu, 2 Apr 2020 11:44:12 +0600 Subject: [OpenStack-Infra] Openstack-documentation publish Message-ID: Hi, I want to publish openstack documentation in my language. Is it possible. If possible please help me how can i do it. -- Thanks with best regards Md. Mohib Billah *Server Administrator and Developer* *Quantum Foundation (ICT)* -------------- next part -------------- An HTML attachment was scrubbed... URL: From aj at suse.com Thu Apr 2 07:23:17 2020 From: aj at suse.com (Andreas Jaeger) Date: Thu, 2 Apr 2020 09:23:17 +0200 Subject: [OpenStack-Infra] Openstack-documentation publish In-Reply-To: References: Message-ID: <6f8142bd-0c50-94fc-9b1e-6c5bc15e230a@suse.com> On 02.04.20 07:44, mohibtech wrote: > Hi, > I want to publish openstack documentation in my language. Is it > possible. If possible please help me how can i do it. Hi, Best to reach out to the i18n team, see docs.openstack.org/i18n/ Andreas -- Andreas Jaeger aj at suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB From cboylan at sapwetik.org Thu Apr 2 21:07:03 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 02 Apr 2020 14:07:03 -0700 Subject: [OpenStack-Infra] Contribution to the OpenStack Infra. In-Reply-To: References: Message-ID: <7d74bcb8-6d37-4af8-b28b-07b622fb9245@www.fastmail.com> On Tue, Mar 31, 2020, at 3:16 PM, Javier Romero wrote: > Hello Team, > > Hope your are well. My name is Javier, live in Argentina and work as a > cloud engineer. Have been working as a Linux sysadmin for the las 10 > years in an Internet service provider. > > > Would like to know if I can start contributing with the OpenStack > Infra. I have expierence with KVM virtualization and Docker containers. > > > > Thank you very much for your attention and sorry for the inconvenience. No thank you! it is not an inconvenience at all. I think we spoke briefly on IRC and my suggestion there was that you look into one of the current efforts that is happening, do some code review to see how pieces fit together and even volunteer to push some changes as you learn. An incomplete but hopefully useful list of activities happening currently: * Deploy Gerrit with Ansible and Docker (migration off of puppet) https://review.opendev.org/#/q/topic:gerrit-docker+status:open * Deploy jitsi meet with etherpad integration for collaborative conference calls and brainstorming (this uses Docker too) https://review.opendev.org/#/q/topic:meetpad+status:open * I think we've recently discovered that we may want to redeploy etherpad under docker for this as well so that we have an up to date installation under the opendev.org domain. https://review.opendev.org/#/c/716442/ * Add Fedora 31 image builds to nodepool so that Zuul jobs can run on Fedora 31 https://review.opendev.org/#/q/(topic:f31+OR+topic:fedora-31)+status:open * Execute our Ansible and Docker config management from Zuul in a CD fashion rather than via cron. https://review.opendev.org/#/q/topic:infra-prod-zuul+status:open I've tried to provide links to inflight changes for each of those efforts. You can review the individual changes there to get an idea for what each of these things involves. Also, I totally understand that this might be a lot to take in. If you pick something that looks interesting and have questions I am more than happy to answer them. Either here on the mailing list or on IRC (I am clarkb). Don't be afraid to ask questions. I have to ask many questions myself :) I hope this helps and let me know if it doesn't (I'll keep trying), Clark From cboylan at sapwetik.org Mon Apr 6 17:47:17 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 06 Apr 2020 10:47:17 -0700 Subject: [OpenStack-Infra] New OpenDev Communication Channels Message-ID: <760c4126-b014-4121-9809-9cf2b613b486@www.fastmail.com> Hello All, Recently, we've transitioned to using #opendev on Freenode for our synchronous IRC communications. Since then we've spun up a new service-discuss at lists.opendev.org mailing list [1] where we'll plan changes to services, notify of meetings, answer questions about services and usage, and otherwise communicate about OpenDev. service-announce at lists.opendev.org [2] will remain for important announcements. If you're interested in the developer infrastructure we run please join us on these mailing lists. We encourage every developer to at least subscribe to the service-announce[2] list. It will be very low traffic, and used only for important announcements with wide impact. We are also going to start having our weekly team meeting in #opendev-meeting. The time will continue to be 19:00 UTC Tuesdays. See you there, Clark [1] http://lists.opendev.org/cgi-bin/mailman/listinfo/service-discuss [2] http://lists.opendev.org/cgi-bin/mailman/listinfo/service-announce From cboylan at sapwetik.org Mon Apr 6 23:59:38 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 06 Apr 2020 16:59:38 -0700 Subject: [OpenStack-Infra] OpenDev team meeting April 7, 2020 Message-ID: <4eb8fa33-4feb-468e-86eb-960b11b08162@www.fastmail.com> Hello, The weekly meeting has a change of venue and will be held in #opendev-meeting. Same time and day: 19:00UTC Tuesdays. Also, going forward I'll be sending the agenda to service-discuss at lists.opendev.org. This week's agenda can be found at: http://lists.opendev.org/pipermail/service-discuss/2020-April/000000.html. Feel free to join the new mailing list as pop in for the meeting tomorrow, Clark From aw442m at att.com Mon Apr 20 14:37:57 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Mon, 20 Apr 2020 14:37:57 +0000 Subject: [OpenStack-Infra] Multi-Source Publishing on docs.airshipit.org Message-ID: <8f0ec3afb0054418a1a3404608b1b692@att.com> Hello! Thank you for giving Airship documentation a home. Having our documentation spread across several Read the Docs sites has long been a frustration for new Airship users. We are excited to fully embrace the site but cannot do so until all of our content is represented there. Since we have many source code repositories, our documentation originates from several different locations. For example, Treasuremap is publishing to docs.airshipit.org; however, Armada documentation [0] is not reachable from that page The Airship Working Committee has considered how to accomplish hosting all of our documentation on the same site while allowing it to live in the same repositories as the corresponding source code. Looking at the publish job [1], it appears that we could accomplish this by removing the final key, adding all of our projects to the "allowed-projects" list, and overriding the "publish_site" variable in repository-specific jobs. For example, we could create a job in the Armada repository that publishes to "airshipit.org/docs/armada" and link to it from our main documentation at docs.airshipit.org. Is our approach feasible given our current setup? If so, the Working Committee will start submitting the necessary changes. Thanks in advance for your help! Best regards, Drew Walters Airship Working Committee [0] https://airshipit.readthedocs.io/projects/armada/en/latest/ [1] https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L452 -------------- next part -------------- An HTML attachment was scrubbed... URL: From aj at suse.com Mon Apr 20 16:29:02 2020 From: aj at suse.com (Andreas Jaeger) Date: Mon, 20 Apr 2020 18:29:02 +0200 Subject: [OpenStack-Infra] Multi-Source Publishing on docs.airshipit.org In-Reply-To: <8f0ec3afb0054418a1a3404608b1b692@att.com> References: <8f0ec3afb0054418a1a3404608b1b692@att.com> Message-ID: <43f1cf65-d070-c96a-4939-e029286bdb34@suse.com> On 20.04.20 16:37, WALTERS, ANDREW wrote: > Hello! > >   > > Thank you for giving Airship documentation a home. Having our > documentation spread across several Read the Docs sites has long been a > frustration for new Airship users. We are excited to fully embrace the > site but cannot do so until all of our content is represented there. > Since we have many source code repositories, our documentation > originates from several different locations. For example, Treasuremap is > publishing to docs.airshipit.org; however, Armada documentation [0] is > not reachable from that page > >   > > The Airship Working Committee has considered how to accomplish hosting > all of our documentation on the same site while allowing it to live in > the same repositories as the corresponding source code. Looking at the > publish job [1], it appears that we could accomplish this by removing > the final key, adding all of our projects to the “allowed-projects” > list, and overriding the “publish_site” variable in repository-specific > jobs. For example, we could create a job in the Armada repository that No, you're not allowed to override the variable. Instead change it to have a variable in it like: publish_site: "airshipit.org/docs/{{ zuul.project.short_name }}" So, create a new job with the changed variable and use that new job everywhere, Andreas > publishes to “airshipit.org/docs/armada” and link to it from our main > documentation at docs.airshipit.org. > >   > > Is our approach feasible given our current setup? If so, the Working > Committee will start submitting the necessary changes. > >   > > Thanks in advance for your help! > >   > > Best regards, > >   > > Drew Walters > > Airship Working Committee > >   > > [0] https://airshipit.readthedocs.io/projects/armada/en/latest/ > > [1] > https://opendev.org/openstack/project-config/src/branch/master/zuul.d/jobs.yaml#L452 > > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > -- Andreas Jaeger aj at suse.com Twitter: jaegerandi SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D 90409 Nürnberg (HRB 36809, AG Nürnberg) GF: Felix Imendörffer GPG fingerprint = EF18 1673 38C4 A372 86B1 E699 5294 24A3 FF91 2ACB From cboylan at sapwetik.org Mon Apr 20 17:40:41 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 20 Apr 2020 10:40:41 -0700 Subject: [OpenStack-Infra] Retiring our puppet modules Message-ID: <9b8db793-4491-4abb-9ed9-a5b0ef33654b@www.fastmail.com> Hello everyone, For a while now we've been slowly moving towards a system that is deployed with less puppet and more ansible+docker. One of the side effects of that is we are no longer effectively maintaining our puppet modules. To make this more clear to people that may be using them, I am writing this email and we are also removing testing from repos that we no longer consume so that they can be formally retired. The first step is job removal which is beginning to happen in this change, https://review.opendev.org/#/c/720900/. The retirement process basically has us update the repo with a commit that removes content and replaces it with a README indicating the repo is retired. This means the process is reversible, the retirement commit can be reverted if necessary. If you are consuming these repos the first step you should take is to checkout the current HEAD commits before any retirement commits land. Then if you intend to keep maintaining the repos let us know and we can probably help you set up forks of some sort to do that. Hopefully, this isn't a surprise as we've been headed in this direction for a while. I wanted to make sure this got communicated directly before we start making downstream visible changes though. Clark From aw442m at att.com Mon Apr 20 19:12:31 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Mon, 20 Apr 2020 19:12:31 +0000 Subject: [OpenStack-Infra] Multi-Source Publishing on docs.airshipit.org In-Reply-To: <43f1cf65-d070-c96a-4939-e029286bdb34@suse.com> References: <8f0ec3afb0054418a1a3404608b1b692@att.com> <43f1cf65-d070-c96a-4939-e029286bdb34@suse.com> Message-ID: > No, you're not allowed to override the variable. Instead change it to have a variable in it like: > publish_site: "airshipit.org/docs/{{ zuul.project.short_name }}" Thanks for your help, Andre! For the mailing list, I have published a change here: https://review.opendev.org/721328 Drew