March 2019 - Airship-discuss - lists.airshipit.org

OSF/Airship Governance and Release Planning Meetings
by Chris Hoge 21 Mar '19

21 Mar '19

The Airship team and OpenStack Foundation have started weekly meetings to help coordinate the release and governance efforts of the Airship project. These meetings, held Fridays at 17:00 UTC/12:00 CDT, are open to the community. We invite you to join us to engage in these, and other topics related to the Airship project. Agenda and connection details in the linked etherpad. https://etherpad.openstack.org/p/2019_Airship_OSF_sync Thanks! Chris Hoge Strategic Program Manager OpenStack Foundation

1 1

Re: [Airship-discuss] Migrating git repos to OpenDev
by corvus＠inaugust.com 21 Mar '19

21 Mar '19

corvus(a)inaugust.com (James E. Blair) writes: > Hi, > > As discussed in November[1], the OpenStack project infrastructure is > being rebranded as "OpenDev" to better support a wider community of > projects. > > We are nearly ready to perform the part of this transition with the > largest impact: moving the authoritative git repositories for existing > projects. Working with the folks representing each of the affected OSF projects, we've scheduled the migration for Friday, April 19, 2019. This is shortly after the next OpenStack release. Please see [2] for further details about what this will involve. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-November/136403.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.ht… -Jim

1 0

Error installing Airship In A Bottle
by Hemanth N 20 Mar '19

20 Mar '19

Hi Nick First thing i would do, is look for apiserver and etcd container errors Can you check the following as well 1. Verify if etcd service is up or not On VM, run netstat -ntulp | grep 2379 2. journalctl -u kubelet.service | grep "Invalid value" Look for errros, it might point out any pod spec issues Also please provide following information 3. cat /etc/kubernetes/manifests/kubernetes-etcd.yaml Check under volumes section if the names have any CAPITAL letters 4. hostname -s My hunch is you have hostname with a CAPS letter which is triggering this failure. Above commands should give an idea if that is the cause. If thats the case, change your hostname to all lowercase and then run airship-in-a-bottle. Regards, Hemanth > Message: 3 > Date: Tue, 12 Mar 2019 17:01:51 -0400 > From: Nick Chase <nchase(a)mirantis.com> > To: "MCEUEN, MATT" <MM9745(a)att.com> > Cc: Evgeny L <eli(a)mirantis.com>, > "airship-discuss(a)lists.airshipit.org" > <airship-discuss(a)lists.airshipit.org> > Subject: Re: [Airship-discuss] Error installing Airship In A Bottle > Message-ID: > <CA+p99G=RzD9+4qAOF5bv-Z=fG0phye=55CxMPnC7bytG+RSg4w(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > OK, so if it IS a timeout thing, if you can tell me how to increase it, > I'll appreciate it, because the script finishes, it just finishes with an > error. > > So the Airship script log is here: http://paste.openstack.org/show/747758/ > Docker processes here: http://paste.openstack.org/show/747759/ > > Thanks.... > > ---- Nick > > > On Wed, Mar 13, 2019 at 6:39 PM MCEUEN, MATT <MM9745(a)att.com> wrote: > > > Agree, and I’d add to check the docker logs of the kube apiserver to make > > sure it’s starting up healthy. > > > > > > > > If you’re not seeing a smoking gun, can you do a `docker ps -a` and > > pastebin the results? > > > > > > > > Thanks, > > > > Matt > > > > > > > > *From:* Evgeny L <eli(a)mirantis.com> > > *Sent:* Wednesday, March 13, 2019 12:59 PM > > *To:* Nick Chase <nchase(a)mirantis.com> > > *Cc:* airship-discuss(a)lists.airshipit.org > > *Subject:* Re: [Airship-discuss] Error installing Airship In A Bottle > > > > > > > > Hi Nick, > > > > > > > > As far as I remember these errors are just retries that wait until > > Kubernetes is up and running, have you tried to wait a bit? > > > > If it still fails for you, can you please send us a complete log? You can > > use http://paste.openstack.org/ > > <https://urldefense.proofpoint.com/v2/url?u=http-3A__paste.openstack.org_&d=…> > > for that. > > > > > > > > Thanks! > > > > > > > > On Mon, Mar 11, 2019 at 8:59 PM Nick Chase <nchase(a)mirantis.com> wrote: > > > > I'm trying to install AIB on a Unbutu Virtualbox VM with 48GB of RAM, 4 > > CPU and a 300GB hard drive. Everything seems to go along fine, until we > > get here: > > > > > > > > Digest: > > sha256:badd2b1da29d4d530b10b920f64bf66a1b41150db46c3c99b49d56f3f18a82db > > Status: Downloaded newer image for > > gcr.io/google_containers/hyperkube-amd64:v1.10.2 > > <https://urldefense.proofpoint.com/v2/url?u=http-3A__gcr.io_google-5Fcontain…> > > Unable to connect to the server: EOF > > .Unable to connect to the server: net/http: request canceled > > (Client.Timeout exceeded while awaiting headers) > > > > > > > > From there, it just keeps giving these two errors. > > > > > > > > Any thoughts? > > > > > > > > Thanks... > > > > > > > > ---- Nick > > > > _______________________________________________ > > Airship-discuss mailing list > > Airship-discuss(a)lists.airshipit.org > > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > <https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi…> > > > > >

3 3

Re: [Airship-discuss] Canceled: Discuss target state implementation of Docker/Kernel/Os/Security Patches etc
by PACHECO, RODOLFO J 20 Mar '19

20 Mar '19

We are moving to a Spec writing Phase for this. Will continue the discussion on the spec , and the Design calls. Thanks for the participation, this is the Etherpad from our discussions: https://etherpad.openstack.org/p/Airship_NodeControlledDeployment Target for an initial Draft for the spec is the Design Call for March 28. Regards Rodolfo Pacheco Home/Office 732 5337671

1 0

Canceled: Discuss target state implementation of Docker/Kernel/Os/Security Patches etc
by PACHECO, RODOLFO J 20 Mar '19

20 Mar '19

We are moving to a Spec writing Phase for this. Will continue the discussion on the spec , and the Design calls. Thanks for the participation, this is the Etherpad from our discussions: https://etherpad.openstack.org/p/Airship_NodeControlledDeployment Target for an initial Draft for the spec is the Design Call for March 28.

1 0

[all][PTG] Strawman Schedule
by Kendall Nelson 19 Mar '19

19 Mar '19

Hello Everyone, In the attached picture or link [0] you will find the proposed schedule for the various tracks at the Denver PTG in April/May. We did our best to avoid the key conflicts that the track leads (PTLs, SIG leads...) mentioned in their PTG survey responses, although there was no perfect solution that would avoid all conflicts especially when the event is three days long and we have over 40 teams meeting. If there is a critical conflict that was missed, please let us know, but otherwise we are not planning to change this proposal. You'll notice that: - Like in Dublin and the last time we were in Denver, a number of tracks do not get pre-allocated time, and will be scheduled on the spot in available rooms at the time that makes the most sense for the participants. - Every track will be able to book extra time and space in available extra rooms at the event via the PTGBot once its configured for the event. More details to come on that. - Airship & OpenStack Helm will each have a day and a half (with the opportunity to book more time as they need) but we hadn't decided which will go first And here are links to more information about the event[1], on registration[2] or booking a room at the event hotel[3] in case you haven't booked or registered yet :) See you there! -Kendall Nelson (diablo_rojo) [0] https://screenshotscdn.firefoxusercontent.com/images/8c880d0a-b41e-4cea-8ff… [1]https://www.openstack.org/ptg [2]https://www.eventbrite.com/e/open-infrastructure-summit-project-teams-gat… [3]https://www.hyatt.com/en-US/group-booking/DENCC/G-FNTE

1 0

Re: [Airship-discuss] Airship-In-A-Bottle_Dev-Single-Node_No-Proxy-Environment_Mass-Ingress_Error
by Loic Le Gal 16 Mar '19

16 Mar '19

> > > Hi everyone, > > Sorry to bother you with this again... I still have a remaining problem to > run airship-in-a-bottle (either dev_single_node or dev_minimal sites: I > target the 1st). > Even going back to previous commits failed: > - some lead to rabbitmq container error > (a9f5fc93e33163f51fc56d1bf886d4d433251f8e) : fixed also by moving from 3.7 > to 3.7.4 (found in later commits) but lead to maas-ingress then mass-import > pb > - maas_ingress error also has been encountered > (539f777c637ffd1927659469072ec6235188b247) patchset 629950 fix this, but I > got stuck to "maas-import-resources' error (previously mentioned in this > thread) > - latest also lead me to this "maas-import-resources error" > In fact 'maas admin boot-resources read' seems to fail a be the root cause > of my problems > > The whole output of kubectl logs of the faulty pod can be found here: > https://drive.google.com/open?id=1smgmynynkUcdtLGw72nbtEXNwXjIW2HH > > Otherwise, as a B plan if I use Airskiff can this fix this problem?and > what will be the next steps to reach the same level than Aiab (ie. K8s + > Openstack running on the same host :a VM) or maybe different VMs will be > required : Build, Genesis and Control + Dataplane? > > Thanks in advance. > BR, > Loïc >

1 0

Discuss target state implementation of Docker/Kernel/Os/Security Patches etc
by PACHECO, RODOLFO J 14 Mar '19

14 Mar '19

When: Occurs every Tuesday from 1:00 PM to 2:00 PM effective 2/26/2019 until 3/29/2019. (UTC-05:00) Eastern Time (US & Canada) Where: https://attcorp.webex.com/join/rp2723 *~*~*~*~*~*~*~*~*~* Reducing to a single day Discuss target state implementation of Airship Docker/Kubelet/Kernel/OS etc upgrade I scheduled a series, will figure out when it’s appropriate What do we need to discuss ? The ability to manage the delivery of any update across groups of hosts in a declarative way. The ability to control disruption effects from those updates Next Meeting: Looking at the https://github.com/GoogleCloudPlatform/metacontroller approach and comparing against what we discussed today. Everyone (in Airship Community) is welcome to participate on this discussions. Approach Discussed on our 1st Meeting https://go.gliffy.com/go/publish/12934972 Sample CR’s .. apiVersion: airship/v1 kind: MultiNodeAction metadata: name: DoSomethingPerRack spec: # List of sets of nodes that theis applies to. Indicates the cadence. 1 set at a time failureSet: set1: rack: rack1 set2: rack: rack2 # - Indicate the Action(What are we doing) - # - Indicate effect Upgrade and Reboot, Reboot Only, .. intentions: - UpgradeDockerAction - UpgradeKubeletAction - RebootAction ## This is teh CR that a node agent consumes apiVersion: airship/v1 kind: NodeAction metadata: name: Set1 spec: setIndicator: rack: rack1 intentions: ListOFActions: - UpgradeDocker - UpgradeKubelet - Reboot ## This is the CR's for ACTIONS that the NodeAgent ingests as well apiVersion: airship/v1 kind: Action metadata: name: Reboot spec: script ..... apiVersion: nc.att.com/v1 kind: Action metadata: name: UpgradeDocker spec: script ..... apiVersion: nc.att.com/v1 kind: Action metadata: name: UpgradeKubelet spec: script .....

1 1

Canceled: Discuss target state implementation of Docker/Kernel/Os/Security Patches etc
by PACHECO, RODOLFO J 14 Mar '19

14 Mar '19

When: Friday, March 15, 2019 1:00 PM-2:00 PM. (UTC-05:00) Eastern Time (US & Canada) Where: https://attcorp.webex.com/join/rp2723 *~*~*~*~*~*~*~*~*~* Reducing to a single day Discuss target state implementation of Airship Docker/Kubelet/Kernel/OS etc upgrade I scheduled a series, will figure out when it’s appropriate What do we need to discuss ? The ability to manage the delivery of any update across groups of hosts in a declarative way. The ability to control disruption effects from those updates Next Meeting: Looking at the https://github.com/GoogleCloudPlatform/metacontroller approach and comparing against what we discussed today. Everyone (in Airship Community) is welcome to participate on this discussions. Approach Discussed on our 1st Meeting https://go.gliffy.com/go/publish/12934972 Sample CR’s .. apiVersion: airship/v1 kind: MultiNodeAction metadata: name: DoSomethingPerRack spec: # List of sets of nodes that theis applies to. Indicates the cadence. 1 set at a time failureSet: set1: rack: rack1 set2: rack: rack2 # - Indicate the Action(What are we doing) - # - Indicate effect Upgrade and Reboot, Reboot Only, .. intentions: - UpgradeDockerAction - UpgradeKubeletAction - RebootAction ## This is teh CR that a node agent consumes apiVersion: airship/v1 kind: NodeAction metadata: name: Set1 spec: setIndicator: rack: rack1 intentions: ListOFActions: - UpgradeDocker - UpgradeKubelet - Reboot ## This is the CR's for ACTIONS that the NodeAgent ingests as well apiVersion: airship/v1 kind: Action metadata: name: Reboot spec: script ..... apiVersion: nc.att.com/v1 kind: Action metadata: name: UpgradeDocker spec: script ..... apiVersion: nc.att.com/v1 kind: Action metadata: name: UpgradeKubelet spec: script .....

1 0

Discuss target state implementation of Docker/Kernel/Os/Security Patches etc
by PACHECO, RODOLFO J 14 Mar '19

14 Mar '19

When: Tuesday, March 12, 2019 1:00 PM-2:00 PM. (UTC-05:00) Eastern Time (US & Canada) Where: https://attcorp.webex.com/join/rp2723 *~*~*~*~*~*~*~*~*~* Discuss target state implementation of Airship Docker/Kubelet/Kernel/OS etc upgrade Etherpad of the ongoing discussion * https://etherpad.openstack.org/p/Airship_NodeControlledDeployment

2 3