Re: [openstack-dev] [openstack-helm] Question about API endpoints

[Hyunsun Moon]

Hi Yoshihiko,

If you have physical LB in your environment, you might want to make use of 
NodePort for distributing the access to multiple controller nodes. In that 
case, it is recommended to set Values.network.external_policy_local to true so 
that you could eliminate unnecessary hops.
Ingress backed by nginx could be used of course, but as you pointed, IP address 
of the node where ingress pod resides will be the address you’re accessing, 
which might not be desirable in many use cases.
If you plan to try it on GCP/GKE, where the ingress controller is backed by 
GCP’s load-balancer service, NodePort + ingress seems valid option for exposing 
your service to external.
FYI, https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer 


Hope this helps.

Hyunsun


> On 5 Mar 2018, at 2:34 PM, 渥美 慶彦  wrote:
> 
> Hi all,
> # Resend with openstack-helm tag
> 
> I try to deploy multinode OpenStack by openstack-helm
> and want to access OpenStack API endpoints from out of k8s nodes.
> To avoid service failure by node down, I think I need one virtual IP for the 
> endpoints.(like Pacemaker)
> Could you show me how to realize that if you have any information?
> 
> A. Deploy OpenStack services for NodePort, and distribute the access to nodes 
> using physical Load Balancer.
> B. Using Ingress?
>   I think Ingress is for L7 routing, so it can't be used to create VIP for 
> the endpoints.
> C. Any other ideas?
> 
> And when I try this on GCP/GKE, is there any difference from on-premises?
> 
> best regards
> 
> -- 
> 
> Yoshihiko Atsumi
> E-mail：atsumi.yoshih...@po.ntt-tx.co.jp
> 
> 
> 
> 
> __
> 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 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] [openstack-helm] Question about API endpoints

[渥美 慶彦]

Hi all,
# Resend with openstack-helm tag

I try to deploy multinode OpenStack by openstack-helm
and want to access OpenStack API endpoints from out of k8s nodes.
To avoid service failure by node down, I think I need one virtual IP for 
the endpoints.(like Pacemaker)

Could you show me how to realize that if you have any information?

A. Deploy OpenStack services for NodePort, and distribute the access to 
nodes using physical Load Balancer.

B. Using Ingress?
  I think Ingress is for L7 routing, so it can't be used to create VIP 
for the endpoints.

C. Any other ideas?

And when I try this on GCP/GKE, is there any difference from on-premises?

best regards

--

Yoshihiko Atsumi
E-mail：atsumi.yoshih...@po.ntt-tx.co.jp




__
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] Question about API endpoints

[渥美 慶彦]

Hi all,

I try to deploy multinode OpenStack by openstack-helm
and want to access OpenStack API endpoints from out of k8s nodes.
To avoid service failure by node down, I think I need one virtual IP for 
the endpoints.(like Pacemaker)

Could you show me how to realize that if you have any information?

A. Deploy OpenStack services for NodePort, and distribute the access to 
nodes using physical Load Balancer.

B. Using Ingress?
  I think Ingress is for L7 routing, so it can't be used to create VIP 
for the endpoints.

C. Any other ideas?

And when I try this on GCP/GKE, is there any difference from on-premises?

best regards

--

Yoshihiko Atsumi
E-mail：atsumi.yoshih...@po.ntt-tx.co.jp




__
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] [devstack] Jens Harbott added to core

[Ian Wienand]

Hello,

Jens Harbott (frickler) has agreed to take on core responsibilities in
devstack, so feel free to bug him about reviews :)

We have also added the members of qa-release in directly to
devstack-core, just for visibility (they already had permissions via
qa-release -> devstack-release -> devstack-core).

We have also added devstack-core as grenade core to hopefully expand
coverage there.

---

Always feel free to give a gentle ping on reviews that don't seem have
received sufficient attention.

But please also take a few minutes to compose a commit message!  I
think sometimes devs have been deep in the weeds with their cool
change and devstack requires just a few tweaks.  It's easy to forget
not all reviewers may have this same context.  A couple of
well-crafted sentences can avoid pulling projects and "git blame"
archaeological digs, which gets everything going faster!

Thanks,

-i

__
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] [Ironic][Bifrost] Manually enrolling a node

[Michael Still]

I think one might be a bug in the deploy guide then. It states:

"In order for nodes to be available for deploying workloads on them, nodes
must be in the available provision state. To do this, nodes created with
API version 1.11 and above must be moved from the enroll state to the
manageable state and then to the available state. This section can be
safely skipped, if API version 1.10 or earlier is used (which is the case
by default)."

Whereas I definitely had to move the node to the manage provision state
manually to get the node to be managed. For reference, this is the set of
command lines I ended up using to manually enroll a node (in case its of
use to someone else):

ironic node-create -d agent_ipmitool \
  -i ipmi_username=root \
  -i ipmi_password=superuser \
  -i ipmi_address=192.168.50.31 \
  -i deploy_kernel=http://192.168.50.209:8080/ipa.vmlinuz \
  -i deploy_ramdisk=http://192.168.50.209:8080/ipa.initramfs \
  -p cpus=16 \
  -p memory_mb=12288 \
  -p local_gb=750 \
  -p cpu_arch=x86_64 \
  -p capabilities=boot_option:local \
  -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  wrote:

> On the enroll state, you can move it to available via manageable by
> setting the provision state to manage, then provide.
>
> Try an ironic node-validate to diagnose the issue, and make sure the ipmi
> credentials given can be used to query the nodes power state using ipmitool.
>
> Mark
>
> On 4 Mar 2018 9:42 p.m., "Mark Goddard"  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 p.m., "Michael Still"  wrote:
>>
>>> Ok, so I applied your patch and redeployed. I now get a list of drivers
>>> in "ironic driver-list", and I can now enroll a node.
>>>
>>> Interestingly, the node sits in the "enroll" provisioning state for ages
>>> and doesn't appear to ever get a meaningful power state (ever being after a
>>> five minute 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  wrote:
>>>
 The ILO hardware type was also not loading because the required
 management and power interfaces were not enabled. The patch should address
 that but please let us know if there are further issues.
 Mark


 On 4 Mar 2018 7:59 p.m., "Michael Still"  wrote:

 Replying to a single email because I am lazier than you.

 I would have included logs, except /var/log/ironic on the bifrost
 machine is empty. There are entries in syslog, but nothing that seems
 related (its all periodic task kind of stuff).

 However, Mark is right. I had an /etc/ironic/ironic.conf with "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.opensta
 ck.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, Mar 5, 2018 at 5:45 AM, Mark Goddard  wrote:

> 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., "Julia Kreger" 
> wrote:
>
>> > No valid host was found. Reason: No conductor service registered
>> which
>> > supports driver agent_ipmitool. (HTTP 400)
>> >
>> > I can't see anything helpful in the logs. What driver should I be
>> using for
>> > bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>>
>> Weird, I'm wondering what the error is in the conductor log. You can
>> try using "ipmi" for the hardware type that replaces
>> agent_ipmitool/pxe_ipmitool.
>>
>> -Julia
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.op
> enstac

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

[Michael Still]

Ahhh yes. The default (null) value of ironic_log_dir doesn't do quite what
the author thought it did. https://review.openstack.org/549650 is a patch
to correct that.

Michael

On Mon, Mar 5, 2018 at 8:42 AM, Mark Goddard  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 p.m., "Michael Still"  wrote:
>
>> Ok, so I applied your patch and redeployed. I now get a list of drivers
>> in "ironic driver-list", and I can now enroll a node.
>>
>> Interestingly, the node sits in the "enroll" provisioning state for ages
>> and doesn't appear to ever get a meaningful power state (ever being after a
>> five minute 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  wrote:
>>
>>> The ILO hardware type was also not loading because the required
>>> management and power interfaces were not enabled. The patch should address
>>> that but please let us know if there are further issues.
>>> Mark
>>>
>>>
>>> On 4 Mar 2018 7:59 p.m., "Michael Still"  wrote:
>>>
>>> Replying to a single email because I am lazier than you.
>>>
>>> I would have included logs, except /var/log/ironic on the bifrost
>>> machine is empty. There are entries in syslog, but nothing that seems
>>> related (its all periodic task kind of stuff).
>>>
>>> However, Mark is right. I had an /etc/ironic/ironic.conf with "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.opensta
>>> ck.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, Mar 5, 2018 at 5:45 AM, Mark Goddard  wrote:
>>>
 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., "Julia Kreger" 
 wrote:

> > No valid host was found. Reason: No conductor service registered
> which
> > supports driver agent_ipmitool. (HTTP 400)
> >
> > I can't see anything helpful in the logs. What driver should I be
> using for
> > bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>
> Weird, I'm wondering what the error is in the conductor log. You can
> try using "ipmi" for the hardware type that replaces
> agent_ipmitool/pxe_ipmitool.
>
> -Julia
>
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.op
> enstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
> __
> 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 Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.or

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

[Mark Goddard]

On the enroll state, you can move it to available via manageable by setting
the provision state to manage, then provide.

Try an ironic node-validate to diagnose the issue, and make sure the ipmi
credentials given can be used to query the nodes power state using ipmitool.

Mark

On 4 Mar 2018 9:42 p.m., "Mark Goddard"  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 p.m., "Michael Still"  wrote:
>
>> Ok, so I applied your patch and redeployed. I now get a list of drivers
>> in "ironic driver-list", and I can now enroll a node.
>>
>> Interestingly, the node sits in the "enroll" provisioning state for ages
>> and doesn't appear to ever get a meaningful power state (ever being after a
>> five minute 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  wrote:
>>
>>> The ILO hardware type was also not loading because the required
>>> management and power interfaces were not enabled. The patch should address
>>> that but please let us know if there are further issues.
>>> Mark
>>>
>>>
>>> On 4 Mar 2018 7:59 p.m., "Michael Still"  wrote:
>>>
>>> Replying to a single email because I am lazier than you.
>>>
>>> I would have included logs, except /var/log/ironic on the bifrost
>>> machine is empty. There are entries in syslog, but nothing that seems
>>> related (its all periodic task kind of stuff).
>>>
>>> However, Mark is right. I had an /etc/ironic/ironic.conf with "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.opensta
>>> ck.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, Mar 5, 2018 at 5:45 AM, Mark Goddard  wrote:
>>>
 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., "Julia Kreger" 
 wrote:

> > No valid host was found. Reason: No conductor service registered
> which
> > supports driver agent_ipmitool. (HTTP 400)
> >
> > I can't see anything helpful in the logs. What driver should I be
> using for
> > bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>
> Weird, I'm wondering what the error is in the conductor log. You can
> try using "ipmi" for the hardware type that replaces
> agent_ipmitool/pxe_ipmitool.
>
> -Julia
>
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.op
> enstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
__
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] [nova] vendordata plugin for freeIPA host enrollment

[Michael Still]

I was thinking about this the other day... How do you de-register instances
from freeipa when the instance is deleted? Is there a missing feature in
vendordata there that you need?

Michael

On Fri, Nov 11, 2016 at 2:01 AM, Rob Crittenden  wrote:

> Wanted to let you know I'm working on a nova metadata vendordata plugin
> that will help automate instance enrollment into a freeIPA server.
>
> This will do a number of things for a user:
> - provide centralized user identity, sudo and host-based access control
> for the instances
> - provide the instance an identity it can use for itself
> - using this identity a host can obtain SSL certificates for itself from
> your freeIPA CA
>
> If ipa_enroll is set to True in the instance metadata (or in the image
> metadata) when a nova instance is spawned then a one-time password will
> be created and IPA enrollment will occur during the cloud-init stage.
>
> Code is currently at https://github.com/rcritten/novajoin
>
> rob
>
> __
> 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 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] [Ironic][Bifrost] Manually enrolling a node

[Mark Goddard]

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 p.m., "Michael Still"  wrote:

> Ok, so I applied your patch and redeployed. I now get a list of drivers in
> "ironic driver-list", and I can now enroll a node.
>
> Interestingly, the node sits in the "enroll" provisioning state for ages
> and doesn't appear to ever get a meaningful power state (ever being after a
> five minute 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  wrote:
>
>> The ILO hardware type was also not loading because the required
>> management and power interfaces were not enabled. The patch should address
>> that but please let us know if there are further issues.
>> Mark
>>
>>
>> On 4 Mar 2018 7:59 p.m., "Michael Still"  wrote:
>>
>> Replying to a single email because I am lazier than you.
>>
>> I would have included logs, except /var/log/ironic on the bifrost machine
>> is empty. There are entries in syslog, but nothing that seems related (its
>> all periodic task kind of stuff).
>>
>> However, Mark is right. I had an /etc/ironic/ironic.conf with "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.opensta
>> ck.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, Mar 5, 2018 at 5:45 AM, Mark Goddard  wrote:
>>
>>> 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., "Julia Kreger" 
>>> wrote:
>>>
 > No valid host was found. Reason: No conductor service registered which
 > supports driver agent_ipmitool. (HTTP 400)
 >
 > I can't see anything helpful in the logs. What driver should I be
 using for
 > bifrost? agent_ipmitool seems to be enabled in ironic.conf.

 Weird, I'm wondering what the error is in the conductor log. You can
 try using "ipmi" for the hardware type that replaces
 agent_ipmitool/pxe_ipmitool.

 -Julia

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> 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 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] [tripleo] upgrading to a containerized undercloud

[Emilien Macchi]

The use case that I'm working on right now is the following:

  As an operator, I would like to upgrade my non-containerized undercloud
running on Queens to a containerized undercloud running on Rocky.
  Also, I would like to maintain the exact same command to upgrade my
undercloud, which is: openstack undercloud upgrade (with --use-heat to
containerize it).

The work has been tracked here:
https://trello.com/c/nFbky9Uk/5-upgrade-support-from-instack-undercloud

But here's an update and some open discussion before we continue to make
progress.

## Workflow

This is what I've found the easiest to implement and maintain:

1) Update python-tripleoclient-* and tripleo-heat-templates.
2) Run openstack overcloud container prepare.
3) Run openstack undercloud upgrade --use-heat, that underneath will: stop
non-containerized services, upgrade all packages & dependencies and deploy
a containerized undercloud.

Note: the data isn't touched, so when the upgrade is done, the undercloud
is just upgraded to Rocky, and containerized.

## Blockers encountered

1) Passwords were re-generated during the containerization, will be fixed
by: https://review.openstack.org/#/c/549600/
2) Neutron DB name was different in instack-undercloud. DB will be renamed
by https://review.openstack.org/#/c/549609/
3) Upgrade logic will live in tripleoclient:
https://review.openstack.org/#/c/549624/ (note that it's small)

## Testing

I'm using https://review.openstack.org/#/c/549611/ for testing but I'm also
deploying in my local environment. I've been upgrading Pike to Queens
successfully, when applying my patches.

## Roadmap

I would like us to solve the containerized undercloud upgrade case by
rocky-m1, and have by the end of m1 a CI job that actually test the
operator workflow.


I'll need some feedback, reviews on the proposal & reviews.
Thanks in advance,
-- 
Emilien Macchi
__
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] [ironic] Polling for new meeting time?

[Zhipeng Huang]

Thx Julia,

Another option is instead of changing meeting time, you could establish a
tick-tock meeting, for example odd weeks for US-Euro friendly times and
even weeks for US-Asia friendly times.

On Mar 4, 2018 7:01 PM, "Julia Kreger"  wrote:

> Greetings everyone!
>
> As our community composition has shifted to be more global, the
> question has arisen if we should consider shifting the meeting to be
> more friendly to some of our contributors in the APAC time zones.
> Alternatively this may involve changing our processes to better plan
> and communicate, but the first step is to understand our overlaps and
> what might work well for everyone.
>
> I have created a doodle poll, from which I would like understand what
> times would ideally work, and from there we can determine if there is
> a better time to meet.
>
> The poll can be found at: https://doodle.com/poll/6kuwixpkkhbwsibk
>
> Please don't feel the need to select times that would be burdensome to
> yourself. This is only to gather information as to the time of day
> that would be ideal for everyone. All times are set as UTC on the
> poll.
>
> Once we have collected some data, we should expect to discuss during
> our meeting on the 12th.
>
> Thanks everyone!
>
> -Julia
>
> __
> 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 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] [Ironic][Bifrost] Manually enrolling a node

[Michael Still]

Ok, so I applied your patch and redeployed. I now get a list of drivers in
"ironic driver-list", and I can now enroll a node.

Interestingly, the node sits in the "enroll" provisioning state for ages
and doesn't appear to ever get a meaningful power state (ever being after a
five minute 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  wrote:

> The ILO hardware type was also not loading because the required management
> and power interfaces were not enabled. The patch should address that but
> please let us know if there are further issues.
> Mark
>
>
> On 4 Mar 2018 7:59 p.m., "Michael Still"  wrote:
>
> Replying to a single email because I am lazier than you.
>
> I would have included logs, except /var/log/ironic on the bifrost machine
> is empty. There are entries in syslog, but nothing that seems related (its
> all periodic task kind of stuff).
>
> However, Mark is right. I had an /etc/ironic/ironic.conf with "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.opensta
> ck.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, Mar 5, 2018 at 5:45 AM, Mark Goddard  wrote:
>
>> 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., "Julia Kreger" 
>> wrote:
>>
>>> > No valid host was found. Reason: No conductor service registered which
>>> > supports driver agent_ipmitool. (HTTP 400)
>>> >
>>> > I can't see anything helpful in the logs. What driver should I be
>>> using for
>>> > bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>>>
>>> Weird, I'm wondering what the error is in the conductor log. You can
>>> try using "ipmi" for the hardware type that replaces
>>> agent_ipmitool/pxe_ipmitool.
>>>
>>> -Julia
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> 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 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 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] [Ironic][Bifrost] Manually enrolling a node

[Mark Goddard]

The ILO hardware type was also not loading because the required management
and power interfaces were not enabled. The patch should address that but
please let us know if there are further issues.
Mark

On 4 Mar 2018 7:59 p.m., "Michael Still"  wrote:

Replying to a single email because I am lazier than you.

I would have included logs, except /var/log/ironic on the bifrost machine
is empty. There are entries in syslog, but nothing that seems related (its
all periodic task kind of stuff).

However, Mark is right. I had an /etc/ironic/ironic.conf with "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, Mar 5, 2018 at 5:45 AM, Mark Goddard  wrote:

> 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., "Julia Kreger" 
> wrote:
>
>> > No valid host was found. Reason: No conductor service registered which
>> > supports driver agent_ipmitool. (HTTP 400)
>> >
>> > I can't see anything helpful in the logs. What driver should I be using
>> for
>> > bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>>
>> Weird, I'm wondering what the error is in the conductor log. You can
>> try using "ipmi" for the hardware type that replaces
>> agent_ipmitool/pxe_ipmitool.
>>
>> -Julia
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> 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 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 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] [Ironic][Bifrost] Manually enrolling a node

[Michael Still]

Replying to a single email because I am lazier than you.

I would have included logs, except /var/log/ironic on the bifrost machine
is empty. There are entries in syslog, but nothing that seems related (its
all periodic task kind of stuff).

However, Mark is right. I had an /etc/ironic/ironic.conf with "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, Mar 5, 2018 at 5:45 AM, Mark Goddard  wrote:

> 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., "Julia Kreger" 
> wrote:
>
>> > No valid host was found. Reason: No conductor service registered which
>> > supports driver agent_ipmitool. (HTTP 400)
>> >
>> > I can't see anything helpful in the logs. What driver should I be using
>> for
>> > bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>>
>> Weird, I'm wondering what the error is in the conductor log. You can
>> try using "ipmi" for the hardware type that replaces
>> agent_ipmitool/pxe_ipmitool.
>>
>> -Julia
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> 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 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] [Ironic][Bifrost] Manually enrolling a node

[Mark Goddard]

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., "Julia Kreger"  wrote:

> > No valid host was found. Reason: No conductor service registered which
> > supports driver agent_ipmitool. (HTTP 400)
> >
> > I can't see anything helpful in the logs. What driver should I be using
> for
> > bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>
> Weird, I'm wondering what the error is in the conductor log. You can
> try using "ipmi" for the hardware type that replaces
> agent_ipmitool/pxe_ipmitool.
>
> -Julia
>
> __
> 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 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] [ironic] Polling for new meeting time?

[Julia Kreger]

Greetings everyone!

As our community composition has shifted to be more global, the
question has arisen if we should consider shifting the meeting to be
more friendly to some of our contributors in the APAC time zones.
Alternatively this may involve changing our processes to better plan
and communicate, but the first step is to understand our overlaps and
what might work well for everyone.

I have created a doodle poll, from which I would like understand what
times would ideally work, and from there we can determine if there is
a better time to meet.

The poll can be found at: https://doodle.com/poll/6kuwixpkkhbwsibk

Please don't feel the need to select times that would be burdensome to
yourself. This is only to gather information as to the time of day
that would be ideal for everyone. All times are set as UTC on the
poll.

Once we have collected some data, we should expect to discuss during
our meeting on the 12th.

Thanks everyone!

-Julia

__
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] [Ironic][Bifrost] Manually enrolling a node

[Julia Kreger]

> No valid host was found. Reason: No conductor service registered which
> supports driver agent_ipmitool. (HTTP 400)
>
> I can't see anything helpful in the logs. What driver should I be using for
> bifrost? agent_ipmitool seems to be enabled in ironic.conf.

Weird, I'm wondering what the error is in the conductor log. You can
try using "ipmi" for the hardware type that replaces
agent_ipmitool/pxe_ipmitool.

-Julia

__
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] [ironic] Re-adding Jim Rollenhagen to ironic-core

[Julia Kreger]

As time goes on it is natural for corporate interests to ebb and flow.
Sometimes this comes as a new side project which complements
OpenStack. Sometimes it is a negative hit where several contributors
are abruptly in search of new jobs. Sadly, I think there is some
normalcy to that. What we do often experience is the reverse reverse
where someone has left[0] and later returns to the community.

Since Jim has resumed working on Ironic[1], I think it naturally makes
sense to add Jim back to ironic-core. This has come up for discussion
several times amongst the ironic-core members over the past two months
since Jim returned, including at the PTG. Every member of ironic-core
has expressed positive feedback to re-adding Jim.

In less than two months, Jim has resumed reviewing[2] and contributing
to ongoing discussions in the community. He has expressed a desire to
help and there is no reason we should deny him the ability.

I will re-add Jim to ironic-core sometime this week if there are no objections.

If anyone objects, please do so promptly.

-Julia

[0] http://lists.openstack.org/pipermail/openstack-dev/2017-June/118036.html
[1] 
http://eavesdrop.openstack.org/irclogs/%23openstack-ironic/%23openstack-ironic.2017-12-06.log.html#t2017-12-06T17:24:39
[2] http://stackalytics.com/report/contribution/ironic/90

__
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] [heat] heat-dashboard is non-free, with broken unit test env

[Thomas Goirand]

On 03/02/2018 07:28 PM, Kaz Shinohara wrote:
> Hi Thomas(zigo),
> 
> I found an issue which is included in
> https://review.openstack.org/#/c/548924/ (you did cherry pick last
> night)
> In short, this issue makes it impossible to install heat-dashboard..
> 
> I landed fix for this.  https://review.openstack.org/#/c/549214/
> 
> Could you kindly pick up this for your package ?
> Sorry again for your inconvenience.
> 
> Regards,
> Kaz(kazsh)

Hi,

I've added the patch, thanks for it.

So now, I'm embedding that patch for fixing unit tests, plus:
https://review.openstack.org/#/c/547468/
https://review.openstack.org/#/c/549214/

Indeed, it'd be nice to have all of them officially backported to
Queens, as you suggested on IRC. It'd be even better to completely
remove embedded stuff, and use xstatic packages. There's already an
XStatic package for the font-awesome which can be used. I do believe it
would be very much OK to add such a requirement to heat-dashboard, since
it is already one of the requirements for Horizon.

Altogether, thanks a lot for your care, as always, the OpenStack
community turns out to be comprehensive, reactive and simply awesome! :)

Cheers,

Thomas Goirand (zigo)

__
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] [Ironic][Bifrost] Manually enrolling a node

[Yolanda Robla Mota]

Hi Michael
So what does ironic driver-list say? May it be pxe_ipmitool? It would also
be useful if you provide the conductor logs.

On Sun, Mar 4, 2018 at 11:06 AM, Michael Still  wrote:

> Heya,
>
> I've been playing with bifrost to help me manage some lab machines. I must
> say the install process was well documented and smooth, so that was a
> pleasure. Thanks!
>
> That said, I am struggling to get a working node enrolment. I'm resisting
> using the JSON file / ansible playbook approach, because I'll want to add
> more machines later so I need a manual enrolment to work. The command line
> I am using is like this:
>
> ironic node-create -d agent_ipmitool \
>-i ipmi_username=root \
>-i ipmi_password=superuser \
>-i ipmi_address=192.168.50.31 \
>-i deploy_kernel=http://192.168.50.209:8080/ipa.vmlinuz \
>-i deploy_ramdisk=http://192.168.50.209:8080/ipa.initramfs \
>-p cpus=16 \
>-p memory_mb=12288 \
>-p local_gb=750 \
>-p cpu_arch=x86_64 \
>-p capabilities=boot_option:local
>
> Unfortunately, I get this error:
>
> No valid host was found. Reason: No conductor service registered which
> supports driver agent_ipmitool. (HTTP 400)
>
> I can't see anything helpful in the logs. What driver should I be using
> for bifrost? agent_ipmitool seems to be enabled in ironic.conf.
>
> Thanks heaps,
> Michael
>
> __
> 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
>
>


-- 

Yolanda Robla Mota

Principal Software Engineer, RHCE

Red Hat



C/Avellana 213

Urb Portugal

yrobl...@redhat.comM: +34605641639


__
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] [Ironic][Bifrost] Manually enrolling a node

[Michael Still]

Heya,

I've been playing with bifrost to help me manage some lab machines. I must
say the install process was well documented and smooth, so that was a
pleasure. Thanks!

That said, I am struggling to get a working node enrolment. I'm resisting
using the JSON file / ansible playbook approach, because I'll want to add
more machines later so I need a manual enrolment to work. The command line
I am using is like this:

ironic node-create -d agent_ipmitool \
   -i ipmi_username=root \
   -i ipmi_password=superuser \
   -i ipmi_address=192.168.50.31 \
   -i deploy_kernel=http://192.168.50.209:8080/ipa.vmlinuz \
   -i deploy_ramdisk=http://192.168.50.209:8080/ipa.initramfs \
   -p cpus=16 \
   -p memory_mb=12288 \
   -p local_gb=750 \
   -p cpu_arch=x86_64 \
   -p capabilities=boot_option:local

Unfortunately, I get this error:

No valid host was found. Reason: No conductor service registered which
supports driver agent_ipmitool. (HTTP 400)

I can't see anything helpful in the logs. What driver should I be using for
bifrost? agent_ipmitool seems to be enabled in ironic.conf.

Thanks heaps,
Michael
__
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