From claire at openstack.org Wed Jul 11 19:14:48 2018 From: claire at openstack.org (Claire Massey) Date: Wed, 11 Jul 2018 14:14:48 -0500 Subject: [Airship-discuss] Berlin Summit CFP Closes July 17 Message-ID: <91A9897D-F82F-4F1F-A73B-3D33585BBBE9@openstack.org> Hi everyone, The CFP deadline for the OpenStack Summit in Berlin is less than one week away, so make sure to submit your talks before July 18 at 6:59am UTC (July 17 at 11:59pm PST). Tracks: • CI/CD • Container Infrastructure • Edge Computing • Hands on Workshops • HPC / GPU / AI • Open Source Community • Private & Hybrid Cloud • Public Cloud • Telecom & NFV SUBMIT HERE Community voting, the first step in building the Summit schedule, will open in mid July. Once community voting concludes, a Programming Committee for each Track will build the schedule. Programming Committees are made up of individuals from many different open source communities working in open infrastructure, in addition to people who have participated in the past. Read the full selection process here . The Summit will take place November 13-15 in Berlin. Register for the Summit - Early Bird pricing ends August 21. Thanks, Claire -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Tue Jul 17 11:54:12 2018 From: paye600 at gmail.com (Roman Gorshunov) Date: Tue, 17 Jul 2018 13:54:12 +0200 Subject: [Airship-discuss] Announcement: Weekly Airship meetings Message-ID: Hello all, Airship developers announce a start of weekly meetings. The first meeting will be held today. Everyone is welcome to participate! Weekly on Tuesday at 1400 UTC in #airshipit @Freenode network IRC: ircs://irc.freenode.net:6697/airshipit Webclient: https://webchat.freenode.net/?randomnick=1&channels=%23airshipit&prompt=1&uio=d4 ICS calendar file for meeting series: http://eavesdrop.openstack.org/calendars/airship-team-meeting.ics Agenda: https://etherpad.openstack.org/p/airship-team-meeting-agenda Chair: Mark Burnett (mark-burnett on Freenode) Logs from past meetings would be here: http://eavesdrop.openstack.org/meetings/airship/ Best regards, -- Roman Gorshunov From claire at openstack.org Tue Jul 17 15:20:05 2018 From: claire at openstack.org (Claire Massey) Date: Tue, 17 Jul 2018 10:20:05 -0500 Subject: [Airship-discuss] Berlin Summit CFP closes in less than 24 hours!! In-Reply-To: <91A9897D-F82F-4F1F-A73B-3D33585BBBE9@openstack.org> References: <91A9897D-F82F-4F1F-A73B-3D33585BBBE9@openstack.org> Message-ID: Hi Airship team, Friendly reminder that the Berlin CFP closes TODAY - July 17 at 11:59pm PST (July 18 at 6:59am UTC), You can submit your talk/panel/workshop proposal here: https://www.openstack.org/summit/berlin-2018/call-for-presentations/ Thanks, Claire > On Jul 11, 2018, at 2:14 PM, Claire Massey wrote: > > Hi everyone, > > The CFP deadline for the OpenStack Summit in Berlin is less than one week away, so make sure to submit your talks before July 18 at 6:59am UTC (July 17 at 11:59pm PST). > > Tracks: > > • CI/CD > • Container Infrastructure > • Edge Computing > • Hands on Workshops > • HPC / GPU / AI > • Open Source Community > • Private & Hybrid Cloud > • Public Cloud > • Telecom & NFV > > SUBMIT HERE > > Community voting, the first step in building the Summit schedule, will open in mid July. Once community voting concludes, a Programming Committee for each Track will build the schedule. Programming Committees are made up of individuals from many different open source communities working in open infrastructure, in addition to people who have participated in the past. Read the full selection process here . > > > The Summit will take place November 13-15 in Berlin. Register for the Summit - Early Bird pricing ends August 21. > > Thanks, > Claire > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Tue Jul 17 15:50:43 2018 From: paye600 at gmail.com (Roman Gorshunov) Date: Tue, 17 Jul 2018 17:50:43 +0200 Subject: [Airship-discuss] Berlin Summit CFP closes in less than 24 hours!! In-Reply-To: References: <91A9897D-F82F-4F1F-A73B-3D33585BBBE9@openstack.org> Message-ID: Claire, Thank you for the information! Best regards, -- Roman Gorshunov On Tue, Jul 17, 2018 at 5:20 PM, Claire Massey wrote: > Hi Airship team, > > Friendly reminder that the Berlin CFP closes TODAY - July 17 at 11:59pm PST > (July 18 at 6:59am UTC), > > You can submit your talk/panel/workshop proposal here: > https://www.openstack.org/summit/berlin-2018/call-for-presentations/ > > Thanks, > Claire > > > On Jul 11, 2018, at 2:14 PM, Claire Massey wrote: > > Hi everyone, > > The CFP deadline for the OpenStack Summit in Berlin is less than one week > away, so make sure to submit your talks before July 18 at 6:59am UTC (July > 17 at 11:59pm PST). > > Tracks: > > • CI/CD > • Container Infrastructure > • Edge Computing > • Hands on Workshops > • HPC / GPU / AI > • Open Source Community > • Private & Hybrid Cloud > • Public Cloud > • Telecom & NFV > > SUBMIT HERE > > Community voting, the first step in building the Summit schedule, will open > in mid July. Once community voting concludes, a Programming Committee for > each Track will build the schedule. Programming Committees are made up of > individuals from many different open source communities working in open > infrastructure, in addition to people who have participated in the past. > Read the full selection process here. > > > The Summit will take place November 13-15 in Berlin. Register for the Summit > - Early Bird pricing ends August 21. > > Thanks, > Claire > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From dd7022 at att.com Thu Jul 19 16:57:29 2018 From: dd7022 at att.com (KATARIA, DEEPAK) Date: Thu, 19 Jul 2018 16:57:29 +0000 Subject: [Airship-discuss] Images missing from quay.io Message-ID: <90BF8249EF30DB4A83C0F4D241F3D72C279FA364@MISOUT7MSGUSRCC.ITServices.sbc.com> Hi: Over the past few weeks, images listed below were removed from quay. What is he policy for updating images in Quay.io ? We have had to get new images via sha# from similar dates. It will nice to keep the images for a longer time, since frequent updates become disruptive in our development quay.io/airshipit/armada at sha256:a404ef890df9b13e621f63f8c5ea9e5d2bb62052531664698769ae750913d693 quay.io/airshipit/armada at sha256:feed50dd4df73ce1271da7ae06970fdbc864807237dc4a9c30038b2d71badf53 quay.io/airshipit/shipyard at sha256:9cd355a4e2c0d44b20aedadcfbe50c83f8d38efc4115834875ada1310d68bd39 quay.io/airshipit/airflow at sha256:fccf9b0ea7ebbc40559b2a7ecee002e13fcad0a43fc4c4bf7689e7e7dcf21787 quay.io/airshipit/drydock at sha256:f096c91df880f4cf2e27a989d02f54cbabefda1d3d918de491112bec965299a6 quay.io/airshipit/deckhand at sha256:34d7c68d8b40049ef32332295484a9a16c8afba41670dfdf51d15bfd3dda3ff7 quay.io/airshipit/sstream-cache at sha256:341684d19882b84acd5f7aec054fd58fb1358edfd87c3c70e32e072ef3cc6c16 quay.io/airshipit/maas-region-controller at sha256:9b723ce5a2d520049e31ff40cca9f91300466d8810377d0fae870522fe530ece quay.io/airshipit/maas-rack-controller at sha256:8886d0110ae3dee2da777e74bc1c9cea23cc5723634bfaa40c0685b902d68f27 Best Regards, Deepak From jr8586335 at gmail.com Sun Jul 22 17:50:40 2018 From: jr8586335 at gmail.com (James Devon) Date: Sun, 22 Jul 2018 19:50:40 +0200 Subject: [Airship-discuss] Redeploy node using armada failed Message-ID: Hello, What is the correct way to reprovision a node and make it join the cluster again using promenade? In the first step of deployment, using promenade, join-nodes.sh scripts are generated. In my case, I create a cluster with 10 nodes including 3 masters. What if I want to reprovision one node? I tries to do kubectl delete node ceph01 and I reinstall the node and give it the same ip and hostname as the previous one and then execute the same join script (which was generated before, and already executed on the previous node before deleting it). The problem is that calico-etcd-ceph01 pods keeps failing. Here is the log http://paste.openstack.org/show/726411/ What should I do to be able to redeploy nodes? Best, -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Mon Jul 23 17:44:08 2018 From: paye600 at gmail.com (Roman Gorshunov) Date: Mon, 23 Jul 2018 19:44:08 +0200 Subject: [Airship-discuss] Redeploy node using armada failed In-Reply-To: References: Message-ID: Hello James, Thank you for trying Airship! Our developer Bryan is currently working on a user story to make Shipyard support a redeploy_server action that will tear down a node and then deploy the node. A few notes about this: 1) we're going initially for a destructive tear down, meaning that the operator has to care for dependent workload moves and control plane adjustments before invoking. 2) there is a longer term plan to make a graceful teardown that will attempt to preserve the health of the control plane proactively, and allow dependent workloads an opportunity to take action before the teardown and redeployment. As for right now, before this story is complete and available, any teardown of a node would be manual, but running an update_site action through Shipyard would trigger the steps to bring the node back in alignment with the committed design for the site. Best regards, -- Roman Gorshunov On Sun, Jul 22, 2018 at 7:50 PM, James Devon wrote: > Hello, > > What is the correct way to reprovision a node and make it join the cluster > again using promenade? > > In the first step of deployment, using promenade, join-nodes.sh scripts are > generated. > > In my case, I create a cluster with 10 nodes including 3 masters. What if I > want to reprovision one node? I tries to do kubectl delete node ceph01 and I > reinstall the node and give it the same ip and hostname as the previous one > and then execute the same join script (which was generated before, and > already executed on the previous node before deleting it). > > The problem is that calico-etcd-ceph01 pods keeps failing. Here is the log > http://paste.openstack.org/show/726411/ > > What should I do to be able to redeploy nodes? > > Best, > > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From jr8586335 at gmail.com Mon Jul 23 19:04:43 2018 From: jr8586335 at gmail.com (James Devon) Date: Mon, 23 Jul 2018 21:04:43 +0200 Subject: [Airship-discuss] Redeploy node using armada failed In-Reply-To: References: Message-ID: Hi, Thanks for your answer. 1. I'm not using shipyard. Instead I am managing my environment with a configuration management tool for now. 2. How can I concretely teardown a node? Is there a command to run? I'm using only armada and promenade. Best, On Mon, Jul 23, 2018, 7:44 PM Roman Gorshunov wrote: > Hello James, > > Thank you for trying Airship! > > Our developer Bryan is currently working on a user story to make > Shipyard support a redeploy_server action that will tear down a node > and then deploy the node. > > A few notes about this: > 1) we're going initially for a destructive tear down, meaning that the > operator has to care for dependent workload moves and control plane > adjustments before invoking. > 2) there is a longer term plan to make a graceful teardown that will > attempt to preserve the health of the control plane proactively, and > allow dependent workloads an opportunity to take action before the > teardown and redeployment. > > As for right now, before this story is complete and available, any > teardown of a node would be manual, but running an update_site action > through Shipyard would trigger the steps to bring the node back in > alignment with the committed design for the site. > > Best regards, > -- > Roman Gorshunov > > On Sun, Jul 22, 2018 at 7:50 PM, James Devon wrote: > > Hello, > > > > What is the correct way to reprovision a node and make it join the > cluster > > again using promenade? > > > > In the first step of deployment, using promenade, join-nodes.sh scripts > are > > generated. > > > > In my case, I create a cluster with 10 nodes including 3 masters. What > if I > > want to reprovision one node? I tries to do kubectl delete node ceph01 > and I > > reinstall the node and give it the same ip and hostname as the previous > one > > and then execute the same join script (which was generated before, and > > already executed on the previous node before deleting it). > > > > The problem is that calico-etcd-ceph01 pods keeps failing. Here is the > log > > http://paste.openstack.org/show/726411/ > > > > What should I do to be able to redeploy nodes? > > > > Best, > > > > > > > > _______________________________________________ > > Airship-discuss mailing list > > Airship-discuss at lists.airshipit.org > > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark.m.burnett at gmail.com Tue Jul 24 18:49:23 2018 From: mark.m.burnett at gmail.com (Mark Burnett) Date: Tue, 24 Jul 2018 13:49:23 -0500 Subject: [Airship-discuss] Redeploy node using armada failed In-Reply-To: References: Message-ID: Hi James, You should be able to remove a node via /user/local/bin/promenade-teardown. That script is used in the resiliency test that is run via tools/gate.sh in the promenade repo. You can find the template for that script here: https://github.com/openstack/airship-promenade/blob/9e0ab1871aad273787cb40f0a591a680633f4ae7/promenade/templates/roles/common/usr/local/bin/promenade-teardown Best, Mark On Mon, Jul 23, 2018 at 2:05 PM James Devon wrote: > Hi, > > Thanks for your answer. > > 1. I'm not using shipyard. Instead I am managing my environment with a > configuration management tool for now. > > 2. How can I concretely teardown a node? Is there a command to run? I'm > using only armada and promenade. > > Best, > > On Mon, Jul 23, 2018, 7:44 PM Roman Gorshunov wrote: > >> Hello James, >> >> Thank you for trying Airship! >> >> Our developer Bryan is currently working on a user story to make >> Shipyard support a redeploy_server action that will tear down a node >> and then deploy the node. >> >> A few notes about this: >> 1) we're going initially for a destructive tear down, meaning that the >> operator has to care for dependent workload moves and control plane >> adjustments before invoking. >> 2) there is a longer term plan to make a graceful teardown that will >> attempt to preserve the health of the control plane proactively, and >> allow dependent workloads an opportunity to take action before the >> teardown and redeployment. >> >> As for right now, before this story is complete and available, any >> teardown of a node would be manual, but running an update_site action >> through Shipyard would trigger the steps to bring the node back in >> alignment with the committed design for the site. >> >> Best regards, >> -- >> Roman Gorshunov >> >> On Sun, Jul 22, 2018 at 7:50 PM, James Devon wrote: >> > Hello, >> > >> > What is the correct way to reprovision a node and make it join the >> cluster >> > again using promenade? >> > >> > In the first step of deployment, using promenade, join-nodes.sh scripts >> are >> > generated. >> > >> > In my case, I create a cluster with 10 nodes including 3 masters. What >> if I >> > want to reprovision one node? I tries to do kubectl delete node ceph01 >> and I >> > reinstall the node and give it the same ip and hostname as the previous >> one >> > and then execute the same join script (which was generated before, and >> > already executed on the previous node before deleting it). >> > >> > The problem is that calico-etcd-ceph01 pods keeps failing. Here is the >> log >> > http://paste.openstack.org/show/726411/ >> > >> > What should I do to be able to redeploy nodes? >> > >> > Best, >> > >> > >> > >> > _______________________________________________ >> > Airship-discuss mailing list >> > Airship-discuss at lists.airshipit.org >> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire at openstack.org Tue Jul 24 21:27:49 2018 From: claire at openstack.org (Claire Massey) Date: Tue, 24 Jul 2018 16:27:49 -0500 Subject: [Airship-discuss] Airship F2F Meeting at PTG Denver - September 2018 In-Reply-To: References: Message-ID: Hi there, The Denver PTG schedule is now available at openstack.org/ptg. Airship has dedicated space reserved on both Monday and Tuesday, September 10-11. This is a great opportunity for the Airship team to meet in person to discuss both project specific items and schedule cross-project collaborative sessions with other participating teams including the Edge Computing Group, StarlingX, OpenStack-Helm and others. Please add your name to the etherpad if you plan to attend https://etherpad.openstack.org/p/AirshipPTG4 and get yourself registered before prices increase on August 24! Thanks, Claire > On Jun 21, 2018, at 9:05 AM, Claire Massey wrote: > > Hello Airship team, > > Myself and other members of the OpenStack Foundation will be working closely with you to provide support and guidance over the coming weeks and months as we work together to organize the project's structure and processes and build out the community. Stay tuned for resources to be shared soon. > > In the meantime I want to make sure you’re aware of and plan to participate in the PTG (https://www.openstack.org/ptg/ ). It's a 5-day long meeting series that provides face to face time for project teams under the OpenStack Foundation umbrella. The next PTG will be held in Denver, Colorado the week of September 10. > > This is a great opportunity for the Airship team to meet in person to discuss both project specific items and schedule cross-project collaborative sessions with other participating teams. Airship will have a dedicated spaced reserved to hold a two-day meeting at the PTG, the exact schedule will be announced later. > > Below you'll find some information from my colleague Kendall on participating teams and administrative info on the PTG. Please make sure you register for the event early (as prices will increase) and have your hotel booked so you don’t miss the discounted rate if you’re planning to attend. > > Add your name to the following etherpad if you plan on attending: https://etherpad.openstack.org/p/AirshipPTG4 and from there we can build out the Airship agenda. > > Feel free to ping me if you have any questions about the information below or about the PTG itself. > > Thanks, > Claire Massey > OpenStack Foundation > > > ----------------------------------------------- > > Hello Everyone! > > Wanted to give you some updates on PTG4 planning. We have finalized the list of SIGs/ Groups/WGs/Teams that are attending. They are as follows: > > * Airship > * API SIG > * Barbican/Security SIG > * Blazar > * Chef OpenStack > * Cinder > * Cyborg > * Designate > * Documentation > * Edge Computing Group > * First Contact SIG > * Glance > * Heat > * Horizon > * Infrastructure > * Interop WG > * Ironic > * Kata > * Keystone > * Kolla > * LOCI > * Manila > * Masakari > * Mistral > * Monasca > * Neutron > * Nova > * Octavia > * OpenStack Ansible > * OpenStack Charms > * OpenStack Helm > * OpenStackClient > * Operator Meetup > * Puppet OpenStack > * QA > * Oslo > * Public Cloud WG > * Release Management > * Requirements > * Sahara > * Scientific SIG > * Self-Healing SIG > * SIG-K8s > * StarlingX > * Swift > * OpenStack TC > * TripleO > * Upgrades SIG > * Watcher > * Zuul (pending confirmation) > > Thierry and I are working on placing them into a strawman schedule to reduce conflicts between related or overlapping groups. We should have more on what that will look like and a draft for you all to review in the next few weeks. > > We also wanted to remind you all of the Travel Support Program. We are again doing a two phase selection. The first deadline is approaching: July 1st. At this point we have less than a dozen applicants so if you need it or even think you need it, I urge you to apply here[1]. > > Also! Reminder that we have a finite number of rooms in the hotel block so please book early to make sure you get the discounted rate before they run out. You can book those rooms here[2] (pardon the ugly URL). > > Can't wait to see you all there! > > -Kendall Nelson (diablo_rojo) > > P.S. Gonna try to do a game night again since you all seemed to enjoy it so much last time :) > > [1] https://openstackfoundation.formstack.com/forms/travelsupportptg_denver_2018 > [2] https://www.marriott.com/meeting-event-hotels/group-corporate-travel/groupCorp.mi?resLinkData=Project%20Teams%20Gathering%2C%20Openstack%5Edensa%60opnopna%7Copnopnb%60149.00%60USD%60false%604%609/5/18%609/18/18%608/20/18&app=resvlink&stop_mobi=yes -------------- next part -------------- An HTML attachment was scrubbed... URL: From jr8586335 at gmail.com Sat Jul 28 17:42:08 2018 From: jr8586335 at gmail.com (James Devon) Date: Sat, 28 Jul 2018 19:42:08 +0200 Subject: [Airship-discuss] Problem during genesis with calico-etcd-anchor and calico-etcd Message-ID: Hello, I've managed to install many kubernetes clusters using promenade, armada. But for some strange reasons the genesis process doesn't work in my current environment. The only difference with my previous environment is that the interface I'm using is a bonded interface. The genesis process get stucks with : Error: unhealthy cluster + date +%s + now=1532799485 + [ 1532799485 -gt 1532799726 ] + sleep 15 + etcdctl member list + grep 192.168.41.244 56c1d8d3e228b500, started, signals01, https://192.168.41.244:6667, https://192.168.41.244:6666 + ETCDCTL_ENDPOINTS=https://192.168.41.244:6666 etcdctl endpoint health https://192.168.41.244:6666 is unhealthy: failed to connect: context deadline exceeded Error: unhealthy cluster + date +%s + now=1532799503 + [ 1532799503 -gt 1532799726 ] + sleep 15 https://pastebin.com/hHsU437T Otherwise the other pods look fine: NAMESPACE NAME READY STATUS RESTARTS AGE kube-system auxiliary-etcd-signals01 3/3 Running 0 37m kube-system bootstrap-armada-signals01 4/4 Running 0 38m kube-system calico-etcd-anchor-5jqdk 0/1 Running 0 30m kube-system calico-etcd-signals01 1/1 Running 0 2m kube-system calico-kube-policy-controllers-54cd86cf9b-5hphl 1/1 Running 4 18m kube-system calico-node-82xqk 2/2 Running 1 26m kube-system calico-settings-v2r2w 0/1 Completed 0 26m kube-system coredns-86d5687d78-gslbp 1/1 Running 0 15m kube-system coredns-86d5687d78-jq2pc 1/1 Running 0 15m kube-system haproxy-anchor-nlpc6 1/1 Running 0 5m kube-system haproxy-signals01 1/1 Running 0 5m kube-system kubernetes-apiserver-signals01 1/1 Running 0 37m kube-system kubernetes-controller-manager-signals01 1/1 Running 0 38m kube-system kubernetes-etcd-signals01 1/1 Running 0 37m kube-system kubernetes-proxy-b9tlx 1/1 Running 0 37m kube-system kubernetes-scheduler-signals01 1/1 Running 0 38m Do you have an idea what could be wrong? Is it possible that bonding might have an impact? I've spend 4 days trying to debug it but no results... Best, James -------------- next part -------------- An HTML attachment was scrubbed... URL: From jr8586335 at gmail.com Mon Jul 30 08:20:44 2018 From: jr8586335 at gmail.com (James Devon) Date: Mon, 30 Jul 2018 10:20:44 +0200 Subject: [Airship-discuss] Problem during genesis with calico-etcd-anchor and calico-etcd In-Reply-To: References: Message-ID: Hi, I've managed to fix it, I think it was due to wrong default routes. So I changed the routes, disabled apparmor and took the latest kernel for Ubuntu Xenial and it works. Best, James On Sat, Jul 28, 2018 at 7:42 PM, James Devon wrote: > Hello, > > I've managed to install many kubernetes clusters using promenade, armada. > But for some strange reasons the genesis process doesn't work in my current > environment. > > The only difference with my previous environment is that the interface I'm > using is a bonded interface. > > The genesis process get stucks with : > > Error: unhealthy cluster > > + date +%s > > + now=1532799485 > > + [ 1532799485 -gt 1532799726 ] > > + sleep 15 > > + etcdctl member list > > + grep 192.168.41.244 > > 56c1d8d3e228b500, started, signals01, https://192.168.41.244:6667, > https://192.168.41.244:6666 > > + ETCDCTL_ENDPOINTS=https://192.168.41.244:6666 etcdctl endpoint health > > https://192.168.41.244:6666 is unhealthy: failed to connect: context > deadline exceeded > > Error: unhealthy cluster > > + date +%s > > + now=1532799503 > > + [ 1532799503 -gt 1532799726 ] > > + sleep 15 > > > https://pastebin.com/hHsU437T > > Otherwise the other pods look fine: > > NAMESPACE NAME READY > STATUS RESTARTS AGE > > kube-system auxiliary-etcd-signals01 3/3 Running > 0 37m > > kube-system bootstrap-armada-signals01 4/4 Running > 0 38m > > kube-system calico-etcd-anchor-5jqdk 0/1 Running > 0 30m > > kube-system calico-etcd-signals01 1/1 Running > 0 2m > > kube-system calico-kube-policy-controllers-54cd86cf9b-5hphl 1/1 Running > 4 18m > > kube-system calico-node-82xqk 2/2 Running > 1 26m > > kube-system calico-settings-v2r2w 0/1 Completed > 0 26m > > kube-system coredns-86d5687d78-gslbp 1/1 Running > 0 15m > > kube-system coredns-86d5687d78-jq2pc 1/1 Running > 0 15m > > kube-system haproxy-anchor-nlpc6 1/1 Running > 0 5m > > kube-system haproxy-signals01 1/1 Running > 0 5m > > kube-system kubernetes-apiserver-signals01 1/1 Running > 0 37m > > kube-system kubernetes-controller-manager-signals01 1/1 Running > 0 38m > > kube-system kubernetes-etcd-signals01 1/1 Running > 0 37m > > kube-system kubernetes-proxy-b9tlx 1/1 Running > 0 37m > > kube-system kubernetes-scheduler-signals01 1/1 Running > 0 38m > > > Do you have an idea what could be wrong? > Is it possible that bonding might have an impact? > I've spend 4 days trying to debug it but no results... > > Best, > James > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dd7022 at att.com Tue Jul 31 18:02:39 2018 From: dd7022 at att.com (KATARIA, DEEPAK) Date: Tue, 31 Jul 2018 18:02:39 +0000 Subject: [Airship-discuss] Issues with QEMU Message-ID: <90BF8249EF30DB4A83C0F4D241F3D72C27A07451@MISOUT7MSGUSRCC.ITServices.sbc.com> Hi: While deploying a sample VNF on airship-in-a-bottle node, we noticed that QEMU is only using one core for an 8 vCPU VM so the software compile is taking a log time. We can see all 8 vCPUs in the VM and work is getting scheduled to all 8, but only one QEMU thread is doing any work. We edited the YAML file to specify the virt_type as KVM and it worked better. Will airship in a bottle team to officially support/test installing with KVM on a bare metal server ? Best Regards, Deepak From mark.m.burnett at gmail.com Tue Jul 31 18:38:16 2018 From: mark.m.burnett at gmail.com (Mark Burnett) Date: Tue, 31 Jul 2018 13:38:16 -0500 Subject: [Airship-discuss] Airship Weekly Meeting Summary 2018-07-31 Message-ID: Hi all, Today's meeting was well attended! Here are some highlights. Meeting schedule: There seems to be some interest from members of the Edge Computing community in participating in future meetings; however, their meeting is scheduled for the same time. We discussed other possible times briefly, but I'd like to open up to the list for candidate times, then we can create a doodle to figure out what works best for everyone. Proposed times: * Tuesdays 13:30-14:00 UTC * Tuesdays 14:00-15:00 UTC (current time) * Tuesdays 16:00-16:30 UTC These all happen to be Tuesdays, but that's not a hard constraint for anyone, as far as I'm aware. Core reviewer list management: The question of how we manage members becoming inactive, and how we consider new cores. There was some discussion, and it's clear we will need to agree on a reasonable and documented approach for this. We can continue the discussion on this list and in the next meeting. PTG Agenda: It's time to start considering topics for the PTG in September. We have two days scheduled. Here is the etherpad so we can start building it out: https://etherpad.openstack.org/p/AirshipPTG4 Next Meeting: Tuesday August 7, at 14:00 UTC in #airshipit. Agenda etherpad: https://etherpad.openstack.org/p/airship-meeting-2018-08-07 And finally, here are the links: * Etherpad: https://etherpad.openstack.org/p/airship-meeting-2018-07-31 * Minutes: http://eavesdrop.openstack.org/meetings/airship/2018/airship.2018-07-31-14.00.html * Minutes (text): http://eavesdrop.openstack.org/meetings/airship/2018/airship.2018-07-31-14.00.txt * Log: http://eavesdrop.openstack.org/meetings/airship/2018/airship.2018-07-31-14.00.log.html Best, Mark Burnett -------------- next part -------------- An HTML attachment was scrubbed... URL: From dd7022 at att.com Tue Jul 31 20:05:44 2018 From: dd7022 at att.com (KATARIA, DEEPAK) Date: Tue, 31 Jul 2018 20:05:44 +0000 Subject: [Airship-discuss] Opening Tickets for Airship-in-a-bottle Message-ID: <90BF8249EF30DB4A83C0F4D241F3D72C27A0751A@MISOUT7MSGUSRCC.ITServices.sbc.com> Hi: Is there a JIRA project set up for Airship-in-a-bottle in Openstack? Please let me know how to log a ticket against the project. If not, what is a way to enter issue items ? Best Regards, Deepak From mark.m.burnett at gmail.com Tue Jul 31 20:17:04 2018 From: mark.m.burnett at gmail.com (Mark Burnett) Date: Tue, 31 Jul 2018 15:17:04 -0500 Subject: [Airship-discuss] Opening Tickets for Airship-in-a-bottle In-Reply-To: <90BF8249EF30DB4A83C0F4D241F3D72C27A0751A@MISOUT7MSGUSRCC.ITServices.sbc.com> References: <90BF8249EF30DB4A83C0F4D241F3D72C27A0751A@MISOUT7MSGUSRCC.ITServices.sbc.com> Message-ID: Hi Deepak, I see you've already found the storyboard group: https://storyboard.openstack.org/#!/project_group/85 Best, Mark On Tue, Jul 31, 2018 at 3:06 PM KATARIA, DEEPAK wrote: > Hi: > > Is there a JIRA project set up for Airship-in-a-bottle in Openstack? > Please let me know how to log a ticket against the project. > If not, what is a way to enter issue items ? > > Best Regards, > > Deepak > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From dd7022 at att.com Tue Jul 31 20:40:42 2018 From: dd7022 at att.com (KATARIA, DEEPAK) Date: Tue, 31 Jul 2018 20:40:42 +0000 Subject: [Airship-discuss] Opening Tickets for Airship-in-a-bottle In-Reply-To: References: <90BF8249EF30DB4A83C0F4D241F3D72C27A0751A@MISOUT7MSGUSRCC.ITServices.sbc.com> Message-ID: <90BF8249EF30DB4A83C0F4D241F3D72C27A07564@MISOUT7MSGUSRCC.ITServices.sbc.com> Hi Mark: Yes, I found out the storyboard group way to enter issues. It works for me. Regards, Deepak From: Mark Burnett [mailto:mark.m.burnett at gmail.com] Sent: Tuesday, July 31, 2018 4:17 PM To: KATARIA, DEEPAK Cc: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Opening Tickets for Airship-in-a-bottle Hi Deepak, I see you've already found the storyboard group: https://storyboard.openstack.org/#!/project_group/85 Best, Mark On Tue, Jul 31, 2018 at 3:06 PM KATARIA, DEEPAK > wrote: Hi: Is there a JIRA project set up for Airship-in-a-bottle in Openstack? Please let me know how to log a ticket against the project. If not, what is a way to enter issue items ? Best Regards, Deepak _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: