[openstack-dev] [kolla] [ironic] Introducing Kayobe - Scientific OpenStack deployment using kolla

Hi, I'd like to announce Kayobe[1], a project that we at StackHPC have been working on recently as we help to build out a performance prototyping platform for the SKA telescope[2]. Kayobe is an open source tool for automating deployment of Scientific OpenStack onto a set of bare metal servers.

Re: [openstack-dev] [kolla] [ironic] Introducing Kayobe - Scientific OpenStack deployment using kolla

nin...@gmail.com> wrote: > Hi，How to join to the project. > > 2017-03-30 16:46 GMT+08:00 Mark Goddard <m...@stackhpc.com>: > >> Hi, >> >> I'd like to announce Kayobe[1], a project that we at StackHPC have been >> working on recently as we help to build out a

Re: [openstack-dev] [openstack-ansible][security] To firewalld, or not to firewalld

In my previous job we had to build a firewall solution for our OpenStack control plane. Our research found that firewalld may have a habit of 'fighting' against the rules added by certain OpenStack services. This was over a year ago, so things may have changed. We didn't pursue firewalld as a

Re: [openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

Hi Pavlo, #3 is used in Bifrost, where there is no Glance service but the default driver is agent_ipmitool. The images are served by the local nginx service. For example, taken from one ironic node: 'image_source': u'http://10.41.253.100:8080/deployment_image.qcow2' Mark On 10 August 2017 at

Re: [openstack-dev] [ironic] support for various glance image reference formats - do we need them all?

red auth etc. > > Cheers, > > On Fri, Aug 11, 2017 at 11:59 AM, Mark Goddard <m...@stackhpc.com> wrote: > >> Hi Pavlo, >> >> #3 is used in Bifrost, where there is no Glance service but the default >> driver is agent_ipmitool. The images

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

I'll throw a second grenade in. Kayobe[1][2] is an OpenStack deployment tool based on kolla-ansible that adds sounds in some ways similar to what you're describing. It roughly follows the TripleO undercloud/overcloud model, with Bifrost used to deploy the overcloud. Kayobe augments kolla-ansible

Re: [openstack-dev] [tripleo] Logging in containerized services

Hi, Kolla-ansible went through this process a few years ago, and ended up with a solution involving heka pulling logs from files in a shared docker volume (kolla_logs). Heka was recently switched for fluentd due to the disappearance of upstream support. I suspect kolla-kubernetes has been through

Re: [openstack-dev] [magnum] Architecture support for either VM or Ironic instance as Containers' Host ?

Hi Greg, You're correct - magnum features support for running on top of VMs or baremetal. Currently baremetal is supported for kubernetes on Fedora core only[1]. There is a cluster template parameter 'server_type', which should be set to 'BM' for baremetal clusters. In terms of how this works

Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

Hi Greg, Magnum clusters currently support using only a single network for all communication. See the heat templates[1][2] in the drivers. . On the bare metal side, currently ironic effectively supports using only a single network interface due to a lack of support for physical network awareness.

Re: [openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

erver > > · but how would other interfaces, get configured on the bare > metal server by ironic ? > > > > > > Greg. > > > > *From: *Mark Goddard <m...@stackhpc.com> > *Reply-To: *"openstack-dev@lists.openstack.org" <ope

Re: [openstack-dev] [ironic][bifrost] Unable to Enroll Inventory

y? Is that the default Ansible > behavior? Is the expectation that I switch to root to install/run > bifrost? > > > I was able to enroll my servers without a hitch. > > Friday I plan to deploy - hopefully I've identified and fixed all the > kinks on my system. > > > T

Re: [openstack-dev] [magnum] magnum cluster-create for kubernetes-template was failed.

Hi, I also hit the loopingcall error while running magnum 4.1.1 (ocata). It is tracked by this bug: https://bugs.launchpad.net/magnum/+bug/1666790. I cherry picked the fix to ocata locally, but this needs to be done upstream as well. I think that the heat stack create timeout is unrelated to

Re: [openstack-dev] [OSC][ironic][mogan] Can we share the same keyword 'baremetal'?

On 25 May 2017 at 11:03, Dmitry Tantsur wrote: > On 05/25/2017 11:38 AM, Zhenguo Niu wrote: > >> >> On Thu, May 25, 2017 at 4:27 PM, Dmitry Tantsur > > wrote: >> >> On 05/25/2017 10:20 AM, Zhenguo Niu wrote: >> >>

Re: [openstack-dev] [tripleo][ironic] Hardware provisioning testing for Ocata

This is great information Justin, thanks for sharing. It will prove useful as we scale up our ironic deployments. It seems to me that a reference configuration of ironic would be a useful resource for many people. Some key decisions affecting scalability and performance may at first seem

[openstack-dev] [ansible][kayobe][kolla] Announcing the availability of kayobe 2.0.0 and 3.0.0

Hi, I am pleased to announce the availability of not one, but two releases of kayobe[1]. Both provide numerous enhancements over previous releases. Kayobe 2.0.0 is based on the Ocata OpenStack release, and Kayobe 3.0.0 on Pike. Please see the release notes[2] for further information. A bit about

Re: [openstack-dev] [ironic] How is the interface for tftpboot server typically configured on OVS ?

Here's an ASCII diagram[1] of the network topology on the controllers of a system we deployed earlier this year using kayobe[2]. As Sam said, we don't touch the neutron OVS bridge, in this case because it's managed entirely by kolla-ansible. Instead, we create a Linux bridge which is plugged into

Re: [openstack-dev] [kolla][vote]Core nomination for Mark Goddard (mgoddard) as kolla core member

; >>> >>> >>> Regards, >>> >>> Duong >>> >>> >>> >>> *From:* Jeffrey Zhang [mailto:zhang.lei@gmail.com] >>> *Sent:* Thursday, April 26, 2018 10:31 PM >>> *To:* OpenStack Development Mailing List <o

Re: [openstack-dev] [kolla][vote] Nominating Steve Noyes for kolla-cli core reviewer

+1 On 1 June 2018 at 08:55, Eduardo Gonzalez wrote: > +1 > > 2018-06-01 8:57 GMT+02:00 Michał Jastrzębski : > >> +1 from me:) >> >> On Thu, May 31, 2018, 11:40 PM Martin André wrote: >> >>> If Steve wrote half of kolla-cli then it's a no brainer to me. +1! >>> >>> On Thu, May 31, 2018 at 7:02

Re: [openstack-dev] [Zun][Kolla][Kolla-ansible] Verify Zun deployment in Kolla gate

Hi, This is something I've been thinking about recently. In particular, I noticed a patch go by to fix the same issue in the magnum role that has been broken and fixed previously. Kolla needs to up its game in terms of CI testing. At the very least, we need tests that verify that services can be

Re: [openstack-dev] [requirements] [vitrage][glance][ironic] global requirements update for python-vitrageclient

Also seeing this for the u-c [1] and g-r [2] bumps for python-ironicclient 2.2.0. These are required in order to use the ironic node traits feature in nova. [1] https://review.openstack.org/#/c/538093 [2] https://review.openstack.org/#/c/538066/3 On 25 January 2018 at 11:15, Afek, Ifat (Nokia -

Re: [openstack-dev] [requirements] [vitrage][glance][ironic] global requirements update for python-vitrageclient

Looks like this should be resolved by https://review.openstack.org/#/c/537453/. Mark On 26 January 2018 at 10:33, Mark Goddard <m...@stackhpc.com> wrote: > Also seeing this for the u-c [1] and g-r [2] bumps for python-ironicclient > 2.2.0. These are required in order to use the

Re: [openstack-dev] [kolla] Policy regarding template customisation

Sometimes there are features that require different containers to be deployed, or different config files to be generated. These are things that cannot be done simply through merging a fixed set of config files. nova_compute_virt_type is an example of such a variable - various non-config tasks

Re: [openstack-dev] [ironic] ansible deploy, playbooks and containers?

I like the swift/HTTP proposal. In kayobe we've considered how to customise the deployment process, with hook points [1] looking like the right approach. Another possibility when deploy steps [2] land could be to break up the ansible deployment into multiple steps, and allow each step to be

Re: [openstack-dev] [kolla] Policy regarding template customisation

I have to agree - I prefer the minimal approach of option 2. It keeps the kolla-ansible code base small and easy to understand. The required test matrix is therefore relatively small (although better coverage of services in CI would be good). Finally, the approach has allowed the project to move

[openstack-dev] [kayobe][kolla] Kayobe IRC channel

Hi, I've registered the #openstack-kayobe channel for developer and operator discussion of kayobe [1]. Jump on if you're using kayobe or interested in doing so. Mark [1] https://github.com/stackhpc/kayobe __ OpenStack

Re: [openstack-dev] [kolla][ptg] Team dinner

+1 On 26 Feb 2018 7:58 p.m., "Eduardo Gonzalez" wrote: > +1 > > On Mon, Feb 26, 2018, 7:40 PM Paul Bourke wrote: > >> Hey Kolla, >> >> Hope you're all enjoying Dublin so far :) Some have expressed interest >> in getting together for a team meal, how

Re: [openstack-dev] [kolla][ptg] Denver PTG on-site or virtual

As one of the lucky three kolleagues able to make the PTG, here's my position (inline). On 17 August 2018 at 11:52, Eduardo Gonzalez wrote: > Fellow kolleages. > > In september is Denver PTG, as per the etherpad [0] only 3 contributors > confirmed their presence in the PTG, we expected more

Re: [openstack-dev] [kolla][ptg] Denver PTG on-site or virtual

t; video of the room and allowing folks to dial in and contribute, while also > having a number of people present physically). > Since the room is already reserved, I don't see a huge point in avoiding > its use either. > > --Adam > > > On Fri, Aug 17, 2018, 20:27 Mark

Re: [openstack-dev] [openstack-ansible][kolla-ansible][tripleo] ansible roles: where they live and what do they do

A couple of changes [1][2] that I proposed to kolla ansible recently as a PoC could be related here. Kolla ansible is full of almost identical roles for each service, with a lot of duplicated 'code' (YAML). The idea was to try to factor some of that out into shared roles. This results in less code

Re: [openstack-dev] [ironic][bifrost][sushy][ironic-inspector][ironic-ui][virtualbmc] sub-project/repository core reviewer changes

+1 On Thu, 23 Aug 2018, 20:43 Jim Rollenhagen, wrote: > ++ > > > // jim > > On Thu, Aug 23, 2018 at 2:24 PM, Julia Kreger > wrote: > >> Greetings everyone! >> >> In our team meeting this week we stumbled across the subject of >> promoting contributors to be sub-project's core reviewers. >>

Re: [openstack-dev] [ironic] proposing metalsmith for inclusion into ironic governance

+1. I like it. Could also be a good fit for Kayobe's undercloud equivalent at some point. On Tue, 28 Aug 2018 at 18:51, Jim Rollenhagen wrote: > On Mon, Aug 27, 2018 at 12:09 PM, Dmitry Tantsur > wrote: > >> Hi all, >> >> I would like propose the metalsmith library [1][2] for inclusion into

Re: [openstack-dev] [kayobe] Kayobe update

On Wed, 22 Aug 2018, 19:08 Erik McCormick, wrote: > > > On Wed, Aug 22, 2018, 1:52 PM Mark Goddard wrote: > >> Hello Kayobians, >> >> I thought it is about time to do another update. >> > > > > >> # PTG >> >> There won't

[openstack-dev] [kayobe] Kayobe update

Hello Kayobians, I thought it is about time to do another update. # Releases Work continues on master adding Kayobe features. We're still deploying the Queens release of OpenStack, although the Rocky patch [1] gets refreshed every so often to ensure we're not lagging behind. I've been

Re: [openstack-dev] [kolla-ansible] how do I unify log data format

Hi Sergey, We are using Kolla Ansible with monasca log API, and have added support for customising the fluentd configuration [1][2]. Doug Szumski (dougsz) made some changes in Queens to try to standardise the log message format. I think Kolla Ansible would benefit from some better documentation

Re: [openstack-dev] [kolla] ptl non candidacy

Thanks for your work as PTL during the Rocky cycle Jeffrey. Hope you are able to stay part of the community. Cheers, Mark On 25 July 2018 at 04:48, Jeffrey Zhang wrote: > Hi all, > > I just wanna to say I am not running PTL for Stein cycle. I have been > involved in Kolla project for almost 3

Re: [openstack-dev] [Kolla] Denver PTG schedule

Looks like the ironic and kolla rooms are next to each other this time, so I can hop between them to help setup the conferencing etc. On Fri, 7 Sep 2018 at 15:21, Mark Goddard wrote: > Thanks for putting that together Eduardo. I've listed the sessions that I > expect to attend below.

Re: [openstack-dev] [Kolla] Denver PTG schedule

Thanks for putting that together Eduardo. I've listed the sessions that I expect to attend below. Mark On Thu, 6 Sep 2018 at 17:40, Eduardo Gonzalez wrote: > Hi folks, > This is the schedule for Kolla Denver PTG. If someone have a hard conflict > with any discussion please let me know if we can

Re: [openstack-dev] [kayobe] Kayobe update

hortly, but > I noted that it should be Tuesday. See you in Denver! > > Cheers, > Erik > > On Wed, Aug 22, 2018 at 5:01 PM Mark Goddard wrote: > > > > > > > > On Wed, 22 Aug 2018, 19:08 Erik McCormick, > wrote: > >> > >> > >> >

[openstack-dev] [ironic] FFE request for node traits

The node traits feature [1] is an essential priority for ironic in Queens, and is an important step in the continuing evolution of scheduling enabled by the placement API. Traits will allow us to move away from capability-based scheduling. Capabilities have several limitations for scheduling

Re: [openstack-dev] [kolla] [tripleo] On moving start scripts out of Kolla images

One benefit of the kolla API that I've not seen mentioned yet (sorry if I missed it) is that you can change files on the host without affecting the running container. Bind mounts don't have this property. This is handy for reconfiguration/upgrade operations, where we write out a new set of config

Re: [openstack-dev] [kolla] [tripleo] On moving start scripts out of Kolla images

On Thu, 5 Apr 2018, 20:28 Martin André, wrote: > On Thu, Apr 5, 2018 at 2:16 PM, Paul Bourke > wrote: > > Hi all, > > > > This mail is to serve as a follow on to the discussion during yesterday's > > team meeting[4], which was regarding the desire to

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

Hi Michael, If you're using the latest release of biifrost I suspect you're hitting https://bugs.launchpad.net/bifrost/+bug/1752975. I've submitted anfox for review. For a workaround, modify /etc/ironic/ironic.conf, and set enabled_hardware_types=ipmi. Cheers, Mark On 4 Mar 2018 5:50 p.m.,

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

nute wait). There are still no logs in /var/log/ironic, and grepping > for the node's uuid in /var/log/syslog returns zero log items. > > Your thoughts? > > Michael > > > > On Mon, Mar 5, 2018 at 7:04 AM, Mark Goddard <m...@stackhpc.com> wrote: > >> The ILO

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

ot;ucs" as a hardware type. I've removed ucs entirely from that list and restarted conductor, but that didn't help. I suspect https://review. openstack.org/#/c/549318/3 is more subtle than that. I will patch in that change and see if I can get things to work after a redeploy. Michael On Mon, Ma

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

p.m., "Mark Goddard" <m...@stackhpc.com> wrote: > Try setting the ironic_log_dir variable to /var/log/ironic, or setting > [default] log_dir to the same in ironic.conf. > > I'm surprised it's not logging to a file by default. > > Mark > > On 4 Mar 2018 8:33

Re: [openstack-dev] [Ironic][Bifrost] Manually enrolling a node

-n lab8 > ironic port-create -n ${UUID} -a ${DHCP_MAC} > ironic node-validate lab8 > ironic --ironic-api-version 1.11 node-set-provision-state lab8 manage > > Michael > > On Mon, Mar 5, 2018 at 9:05 AM, Mark Goddard <m...@stackhpc.com> wrote: > >> On the enroll stat

[openstack-dev] [kayobe] development process changes

Hi Kayobe team, As many of you are aware, we are making the changes necessary [1] to become an OpenStack-related project. This will affect development and use of kayobe in a number of ways. Storyboard We'll be moving from using Github as our issue & feature tracker to Storyboard [2]. See the

[openstack-dev] [kayobe] Kayobe update

Hi all, I thought it might be useful to start an irregular update on Kayobe, covering recent and upcoming events. This follows on from the update blog article [1] that I wrote a couple of months ago (which includes a video and asciinema demo!). # OpenStack-related The switch to using OpenStack

[openstack-dev] [kayobe][kolla] Announcing the release of Kayobe 4.0.0

Hi, Announcing the release of Kayobe 4.0.0. This release includes support for the Queens release of OpenStack, and is the first release of Kayobe built using the OpenStack infrastructure. Release notes:

Re: [openstack-dev] [kolla][iconic] baremetal network

Hi Manuel, You can configure the neutron tenant network types in kolla-ansible via the 'neutron_tenant_network_types' variable in globals.yml. It's a comma-separated list. The default for that variable is vxlan, it's expected that you set it to match your requirements. The

Re: [openstack-dev] [ironic] Tenks

On Wed, 3 Oct 2018 at 17:10, James LaBarre wrote: > On 10/2/18 10:37 AM, Mark Goddard wrote: > > > > On Tue, 2 Oct 2018 at 14:03, Jay Pipes wrote: > >> On 10/02/2018 08:58 AM, Mark Goddard wrote: >> > Tenks is a project for managing 'virtual bare metal clu

Re: [openstack-dev] [kolla-ansible][zun] Request to make another release for stable/queens

Hi Hongbin, I'll add this to our meeting agenda for tomorrow, but I see no reason why we should not make another queens series release. Cheers, Mark On Sun, 7 Oct 2018 at 18:50, Hongbin Lu wrote: > Hi Kolla team, > > I have a fixup on the configuration of Zun service: >

Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

On Tue, 9 Oct 2018 at 12:03, Florian Engelmann < florian.engelm...@everyware.ch> wrote: > Am 10/9/18 um 11:04 AM schrieb Mark Goddard: > > Thanks for these suggestions Florian, there are some interesting ideas > > in here. I'm a little concerned about the maintenan

Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

Thanks for these suggestions Florian, there are some interesting ideas in here. I'm a little concerned about the maintenance overhead of adding support for all of these things, and wonder if some of them could be done without explicit support in kolla and kolla-ansible. The kolla projects have

Re: [openstack-dev] [kolla] add service discovery, proxysql, vault, fabio and FQDN endpoints

On Wed, 10 Oct 2018 at 08:08, Florian Engelmann < florian.engelm...@everyware.ch> wrote: > Am 10/9/18 um 1:47 PM schrieb Mark Goddard: > > > > > > On Tue, 9 Oct 2018 at 12:03, Florian Engelmann > > mailto:florian.engelm...@everyware.ch>> > > > w

[openstack-dev] [ironic] Tenks

Hi, In the most recent Ironic meeting we discussed [1] tenks, and the possibility of adding the project under Ironic governance. We agreed to move the discussion to the mailing list. I'll introduce the project here and give everyone a chance to ask questions. If things appear to move in the right

Re: [openstack-dev] [ironic] Tenks

On Tue, 2 Oct 2018 at 14:03, Jay Pipes wrote: > On 10/02/2018 08:58 AM, Mark Goddard wrote: > > Hi, > > > > In the most recent Ironic meeting we discussed [1] tenks, and the > > possibility of adding the project under Ironic governance. We agreed to > > move t

Re: [openstack-dev] [Openstack-operators] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On Tue, 2 Oct 2018 at 17:10, Jim Rollenhagen wrote: > On Tue, Oct 2, 2018 at 11:40 AM Eric Fried wrote: > >> > What Eric is proposing (and Julia and I seem to be in favor of), is >> > nearly the same as your proposal. The single difference is that these >> > config templates or deploy templates

Re: [openstack-dev] [placement] The "intended purpose" of traits

To add some context around what I suspect is the reason for the most recent incarnation of this debate, many Ironic users have a requirement to be able to influence the configuration of a server at deploy time, beyond the existing supported mechanisms. The classic example is hardware RAID - the

Re: [openstack-dev] [placement] The "intended purpose" of traits

On Fri, 28 Sep 2018 at 22:07, melanie witt wrote: > On Fri, 28 Sep 2018 15:42:23 -0500, Eric Fried wrote: > > On 09/28/2018 09:41 AM, Balázs Gibizer wrote: > >> > >> > >> On Fri, Sep 28, 2018 at 3:25 PM, Eric Fried wrote: > >>> It's time somebody said this. > >>> > >>> Every time we turn a

Re: [openstack-dev] [ironic] [nova] [tripleo] Deprecation of Nova's integration with Ironic Capabilities and ComputeCapabilitiesFilter

On Tue, 25 Sep 2018 at 14:37, John Garbutt wrote: > On Thu, 20 Sep 2018 at 16:02, Matt Riedemann wrote: > >> On 9/20/2018 4:16 AM, John Garbutt wrote: >> > Following on from the PTG discussions, I wanted to bring everyone's >> > attention to Nova's plans to deprecate ComputeCapabilitiesFilter,

Re: [openstack-dev] [kolla] Proposing Chason Chan (chason) as kolla-ansible core

+1 On Tue, 25 Sep 2018 at 16:48, Eduardo Gonzalez wrote: > Hi, > > I would like to propose Chason Chan to the kolla-ansible core team. > > Chason is been working on addition of Vitrage roles, rework VpnaaS > service, maintaining > documentation as well as fixing many bugs. > > Voting will be

Re: [openstack-dev] [kolla] Berlin summit resume

Thanks for the write up Eduardo. I thought you and Surya did a good job of presenting and moderating those sessions. Mark On Wed, 21 Nov 2018 at 17:08, Eduardo Gonzalez wrote: > Hi kollagues, > > During the Berlin Summit kolla team had a few talks and forum discussions, > as well as other

[openstack-dev] [kayobe] Stein forum topics

Hi, Brainstorming for the Stein forum in Berlin has started, please add your proposal topics before 26th September to https://etherpad.openstack.org/p/kayobe-stein-forum. Forum topics are proposed using the same CFP method as Summit presentations: