Re: [openstack-dev] [magnum] [Rocky] K8 deployment on fedora-atomic is failed
y not found (/atomic.io > <http://atomic.io>) [3] > Nov 29 11:05:47 kube-cluster1-qobaagdob75g-master-0.novalocal > flanneld[6491]: E1129 11:05:47.673062 6491 network.go:102] failed > to retrieve network config: 100: Key not found (/atomic.io > <http://atomic.io>) [3] > Nov 29 11:05:48 kube-cluster1-qobaagdob75g-master-0.novalocal > flanneld[6491]: E1129 11:05:48.686919 6491 network.go:102] failed > to retrieve network config: 100: Key not found (/atomic.io > <http://atomic.io>) [3] > Nov 29 11:05:49 kube-cluster1-qobaagdob75g-master-0.novalocal > flanneld[6491]: E1129 11:05:49.709136 6491 network.go:102] failed > to retrieve network config: 100: Key not found (/atomic.io > <http://atomic.io>) [3] > Nov 29 11:05:50 kube-cluster1-qobaagdob75g-master-0.novalocal > flanneld[6491]: E1129 11:05:50.729548 6491 network.go:102] failed > to retrieve network config: 100: Key not found (/atomic.io > <http://atomic.io>) [3] > Nov 29 11:05:51 kube-cluster1-qobaagdob75g-master-0.novalocal > flanneld[6491]: E1129 11:05:51.749425 6491 network.go:102] failed > to retrieve network config: 100: Key not found (/atomic.io > <http://atomic.io>) [3] > Nov 29 11:05:52 kube-cluster1-qobaagdob75g-master-0.novalocal > flanneld[6491]: E1129 11:05:52.776612 6491 network.go:102] failed > to retrieve network config: 100: Key not found (/atomic.io > <http://atomic.io>) [3] > Nov 29 11:05:53 kube-cluster1-qobaagdob75g-master-0.novalocal > flanneld[6491]: E1129 11:05:53.790418 6491 network.go:102] failed > to retrieve network config: 100: Key not found (/atomic.io > <http://atomic.io>) [3] > ~~~ > > - Continuously in the jouralctl logs following messages are printed. > > ~~~ > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > kube-apiserver[6888]: F1129 11:06:39.338416 6888 server.go:269] > Invalid Authorization Config: Unknown authorization mode Node specified > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > systemd[1]: kube-apiserver.service: Main process exited, code=exited, > status=255/n/a > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > kube-scheduler[2540]: E1129 11:06:39.408272 2540 reflector.go:199] > k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:463 > <http://k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:463>: > Failed to list *api.Node: Get > http://127.0.0.1:8080/api/v1/nodes?resourceVersion=0: dial tcp > 127.0.0.1:8080 <http://127.0.0.1:8080>: getsockopt: connection refused > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > kube-scheduler[2540]: E1129 11:06:39.444737 2540 reflector.go:199] > k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:460 > <http://k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:460>: > Failed to list *api.Pod: Get > http://127.0.0.1:8080/api/v1/pods?fieldSelector=spec.nodeName%21%3D%2Cstatus.phase%21%3DFailed%2Cstatus.phase%21%3DSucceeded=0: > dial tcp 127.0.0.1:8080 <http://127.0.0.1:8080>: getsockopt: > connection refused > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > kube-scheduler[2540]: E1129 11:06:39.445793 2540 reflector.go:199] > k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:466 > <http://k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:466>: > Failed to list *api.PersistentVolume: Get > http://127.0.0.1:8080/api/v1/persistentvolumes?resourceVersion=0: dial > tcp 127.0.0.1:8080 <http://127.0.0.1:8080>: getsockopt: connection refused > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 > subj=system_u:system_r:init_t:s0 msg='unit=kube-apiserver > comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? > terminal=? res=failed' > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > systemd[1]: Failed to start Kubernetes API Server. > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > systemd[1]: kube-apiserver.service: Unit entered failed state. > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > systemd[1]: kube-apiserver.service: Failed with result 'exit-code'. > Nov 29 11:06:39 kube-cluster1-qobaagdob75g-master-0.novalocal > kube-scheduler[2540]: E1129 11:06:39.611699 2540 reflector.go:199] > k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:481 > <http://k8s.io/kubernetes/plugin/pkg/scheduler/factory/factory.go:481>: > Failed to list *extensions.ReplicaSet: Get > http://127.0.0.1:8080/apis/extensions/v1beta1/replicasets?resourceVersion=0: > dial tcp 127.0.0.1:8080 <http://127.0.0.1:8080>: getsockopt: > connection refused > ~~~ >
Re: [openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?
//lists.openstack.org/pipermail/openstack-dev/2017-October/123312.html
>>
>>
>> To be clear, for me at least there's only one wrong answer ("person
>> who needs somewhere to run their IRC bouncer"). What's important in
>> my opinion is that we have a bunch of people with *different* answers
>> on the TC, because I think that will lead to better discussion and
>> hopefully better decisions.
>>
>> Discuss.
>>
>> cheers,
>> Zane.
>
>
> __
>
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Cheers & Best regards,
Feilong Wang (王飞龙)
--
Senior Cloud Software Engineer
Tel: +64-48032246
Email: flw...@catalyst.net.nz
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
--
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tc][election] Question for candidates: How do you think we can make our community more inclusive?
Thanks for asking, Flavio. That's one of the topic I mentioned in my candidacy, that's because as a Chinese working on OpenStack in the past 6 years, I do have some experiences about this though I agree it couldn't be done in 1 cycle/year. But I think it's still a domain I can contribute for OpenStack. I can still remember I had to join the Glance meeting at 2:00AM, and was challenged because of saying "Hi guys" in a public channel though "Hi guys" is used very common in New Zealand. Should we expect a non-English native speaker to understand the details between “Hi there", "Hi guys" and "Hi folks"? I think that's the language and culture barrier for many new contributors. We (Brian, Erno） even tried to propose a panel at summit to discuss it before. Currently, it's more important than ever to keep those new contributors due to the changes happening around OpenStack nowadays. On 14/10/17 01:45, Flavio Percoco wrote: > Greetings, > > Some of you, TC candidates, expressed concerns about diversity and > inclusiveness > (or inclusivity, depending on your taste) in your candidacy. I believe > this is a > broad, and some times ill-used, topic so, I'd like to know, from > y'all, how you > think we could make our community more inclusive. What areas would you > improve > first? > > Thank you, > Flavio > > -- > @flaper87 > Flavio Percoco > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Cheers & Best regards, Feilong Wang (王飞龙) -- Senior Cloud Software Engineer Tel: +64-48032246 Email: flw...@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Zaqar] Nominating gecong for Zaqar core
Hi team, I would like to propose adding Cong Ge(gecong) for the Zaqar core team. He has been an awesome contributor since joining the Zaqar team. And now he is currently the most active non-core reviewer on Zaqar projects for the last 180 days[1]. Cong has great technical expertise and contributed many high quality patches. I'm sure he would be an excellent addition to the team. If no one objects, I'll proceed and add him in a week from now. Thanks. [1] http://stackalytics.com/report/contribution/zaqar-group/180 -- Cheers & Best regards, Feilong Wang (王飞龙) -- Senior Cloud Software Engineer Tel: +64-48032246 Email: flw...@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tc][election] TC candidacy
Hi everyone, I'm announcing my candidacy for a position on the OpenStack Technical Committee. For those of you who don't know me yet, I'm Feilong Wang, currently working for Catalyst Cloud as a development lead. Catalyst Cloud is a public cloud running on OpenStack based in New Zealand. Also, I've been serving as the PTL of Zaqar (OpenStack Messaging Service) for 5 cycles. Before that, I was mainly working for Glance (OpenStack Image Service) as a core reviewer since Folsom 2012. Currently the role of the TC is more important than ever. Some large companies are downsizing their investment for OpenStack or switching their focus to containers/k8s, but meanwhile many companies from APAC, especially China, are heavily investing OpenStack. Although it's a pain to lose great contributors, the companies having real requirements for OpenStack are kept. It's a good time for us to think about how to define OpenStack, for whom we're building the software and how to build a collaborative/integrated community. As a TC member I want to bring focus in below areas: #1 Users & Operators Listen closely to the voice of users and operators and this pretty much align with the mission of OpenStack as below. "To produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable." To implement a useful, stable cloud platform, we can't work behind closed doors, but closely work with the user and operator community. As far as I know, except the user survey, we don't have more formal processes/approaches to collect the feedback from our users and operators, though the operators mailing list and some random forum sessions at OpenStack summit are helpful. And IMHO, currently we’re mixing feedback collected from different perspectives. For example, most of the feedback from operators are how to easily deploy/manage the cloud. But the tenant user/developers' requirements are more related to functions, UX, etc. I can see we have put a lot of effort to address the pain of operators, but obviously, we do also need more work to make the tenant users/developer’s life easier. #2 Core and Ecosystem, Big Tent and Constellation As the PTL of Zaqar, an official but not core project, I'm keen to help the evolution at this area. From stackforge to big tent to constellation, we're continuing to explore different approaches to embrace the challenge. So far, we have generally got some positive responses for the idea of constellation, but we do need more details to shape it. And I’m happy to raise my hand. Personally, I’d like to see a focal point/TC member is assigned for each important use-case/constellation, who will be responsible for driving the collaboration and integration for that user case. #3 Diversity and Inclusion Though OpenStack is a community with good diversity and inclusion, we do still need some work at this area given there are more and more contributors from different countries with different languages and cultures. As a Chinese living in New Zealand, I truly understand the pain of crossing/removing the language and culture barrier. I have been working with world wide contributors for the past 5 years, so I believe I can help at this area by sharing/documenting my experience and drive some activities to bridge the different languages and cultures in OpenStack community. #4 Integration and Collaboration As a distributed cloud platform, it's good to decouple different services to make each service do one thing well. However, seems most of projects are solely focusing on their own offering and not enough projects are paying attention to the global impact. I would like to push a more tighter collaboration between projects and obviously it will make the integration more easier and efficient. Operators should expect different projects can work together smoothly just like they're different parts within one project. As a maintainer of a public cloud running on OpenStack, I know the pain of our ops, when they try to migrate a service or adding a new service in existing cluster. So I'd like to see more interlocks between PTL and TC members to understand the gaps and fill the gaps. It would be an honor to be member of your technical committee. Thanks for your consideration! -- Cheers & Best regards, Feilong Wang (王飞龙) -- Senior Cloud Software Engineer Tel: +64-48032246 Email: flw...@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tc] [election] NON nomination for TC
Thank you for all your hard work and serving as a great role model, Sean. On 03/10/17 05:03, Sean Dague wrote: > I'd like to announce that after 4 years serving on the OpenStack > Technical Committee, I will not be running in this fall's > election. Over the last 4 years we've navigated some rough seas > together, including the transition to more inclusion of projects, the > dive off the hype curve, the emergence of real interoperability > between clouds, and the beginnings of a new vision of OpenStack > pairing with more technologies beyond our community. > > There remains a ton of good work to be done. But it's also important > that we have a wide range of leaders to do that. Those opportunities > only exist if we make space for new leaders to emerge. Rotational > leadership is part of what makes OpenStack great, and is part of what > will ensure that this community lasts far beyond any individuals > within it. > > I plan to still be around in the community, and contribute where > needed. So this is not farewell. However it will be good to see new > faces among the folks leading the next steps in the community. > > I would encourage all members of the community that are interested in > contributing to the future of OpenStack to step forward and run. It's > important to realize what the TC is and can be. This remains a > community driven by consensus, and the TC reflects that. Being a > member of the TC does raise your community visibility, but it does not > replace the need to listen, understand, communicate clearly, and > realize that hard work comes through compromise. > > Good luck to all our candidates this fall, and thanks for letting me > represent you the past 4 years. > > -Sean > -- Cheers & Best regards, Feilong Wang (王飞龙) -- Senior Cloud Software Engineer Tel: +64-48032246 Email: flw...@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all][tc] How to deal with confusion around "hosted projects"
On 15/07/17 03:45, Ed Leafe wrote: On Jul 13, 2017, at 10:32 PM, Fei Long Wang <feil...@catalyst.net.nz> wrote: I agree with Zane for most of the parts. But one thing I don't really understand is, why OpenStack community is still confusing at the IaaS, PaaS and SaaS, does the classification really mater at nowadays? Do we really need a label/tag for OpenStack to limit it as an IaaS, PaaS or SaaS? I never see AWS says it's an IaaS, PaaS or SaaS. Did Azure or Google Cloud say that? I think they're just providing the service their customer want. Sure, they may not distinguish those things publicly, but in their internal development teams it is very likely that they understand these boundaries. And just for another quick example, from the Azure site: https://azure.microsoft.com/en-us/overview/azure-vs-aws/ "We are the only cloud provider recognized in the industry as having leading solutions in IaaS, PaaS, and SaaS. And Azure PaaS platform services can help you be more productive and increase your ROI according to this Forrester Total Economic Impact study.” So I don’t think that this distinction is peculiar to OpenStack. Yep, there is no conflict between you and me. It's good to understand the XaaS boundary within OpenStack community, such as there is no argument to say Zaqar is a PaaS layer service. What I'm saying is, is it really necessary to limit OpenStack only on IaaS? I can see the contradiction happening in OpenStack community. OpenStack are successful on the IaaS layer as a de facto open standard. So we'd like to grow to get a big success. But we're running into some troubles because we're running too fast. Then some people said, we should stop grow the scope of OpenStack, let's just focus on IaaS. However, that shouldn't be the excuse to stop building a better ecosystem around OpenStack. If the classification is really matter, then we can define (we already have?) the core service at IaaS layer. But I still want to see some upper layer services within OpenStack community, such as LBaaS, DNSaaS, MQaaS, etc, etc. Just my $0.02 -- Ed Leafe __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Cheers & Best regards, Feilong Wang (王飞龙) -- Senior Cloud Software Engineer Tel: +64-48032246 Email: flw...@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [glance] Stepping down from core
Hi there, I've been a Glance core since 2013 and been involved in the Glance community even longer, so I care deeply about Glance. My situation right now is such that I cannot devote sufficient time to Glance, and while as you've seen elsewhere on the mailing list, Glance needs reviewers, I'm afraid that keeping my name on the core list is giving people a false impression of how dire the current Glance personnel situation is. So after discussed with Glance PTL, I'd like to offer my resignation as a member of the Glance core reviewer team. Thank you for your understanding. -- Cheers & Best regards, Feilong Wang (王飞龙) -- Senior Cloud Software Engineer Tel: +64-48032246 Email: flw...@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance] nominating Mike Fedosin for glance core
Welcome back, Mike. On 26/05/17 16:21, Kekane, Abhishek wrote: +1, agree with Nikhil. Abhishek *From:*Nikhil Komawar [mailto:nik.koma...@gmail.com] *Sent:* Friday, May 26, 2017 6:04 AM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [glance] nominating Mike Fedosin for glance core This is great news. Always +2 for Mike, he's been great (dev, glancer, stacker ..) all the years. Let's not wait so long for reinstatement if folks are on-board, as having another core will only help. On Thu, May 25, 2017 at 11:53 AM, Brian Rosmaita <rosmaita.foss...@gmail.com <mailto:rosmaita.foss...@gmail.com>> wrote: As you've no doubt read elsewhere on the ML, we've lost several glance cores recently due to employment changes. Luckily, Mike Fedosin informed me at today's Glance weekly meeting that he will have time for the next few months to devote some time to Glance reviewing. For those who don't know Mike (mfedosin on IRC), he was a Glance core for several years. He provided a lot of notes that were used to write the Glance architecture documentation that is so helpful to new contributors, so he's extremely knowledgeable about the design patterns used in Glance. Most recently, Mike's been working on the Glare project, which has a lot in common with Glance. While Mike says he can't commit much time to Glance development, he has proposed porting some of the Glare tests over to Glance, which will certainly help with our code coverage, and would be a helpful addition to Glance. (Mike agreed at today's Glance meeting not to propose re-integrating Glare into the Glance project until the Queens PTG (if at all), so I'm not worried about that being a distraction during the Pike cycle when we are so short-handed.) I'd like to reinstate Mike as a Glance core contributor at the next Glance weekly meeting. Please reply to this message with any comments or concerns before 23:59 UTC on Wednesday 31 May 2017. cheers, brian __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- -- Thanks, Nikhil __ Disclaimer: This email and any attachments are sent in strictest confidence for the sole use of the addressee and may contain legally privileged, confidential, and proprietary data. If you are not the intended recipient, please advise the sender by replying promptly to this email and then delete and destroy this email and any attachments without any further use, copying or forwarding. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Cheers & Best regards, Feilong Wang (王飞龙) -- Senior Cloud Software Engineer Tel: +64-48032246 Email: flw...@catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [zaqar] Design Summit Schedule
Hi All, As we discussed, I've pushed the final design summit schedule[1][2] for Zaqar. Please take a look and let me know if there is anything we need to change to avoid conflicts. [1] https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Zaqar [2] https://wiki.openstack.org/wiki/Design_Summit/Ocata/Etherpads#Zaqar -- Cheers & Best regards, Fei Long Wang (王飞龙) -- Senior Cloud Software Engineer Tel: +64-48032246 Email: flwang at catalyst.net.nz Catalyst IT Limited Level 6, Catalyst House, 150 Willis Street, Wellington -- __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
