Re: [openstack-dev] [kolla] Gate precheck job failed due to minimum kernel version on ubuntu 14.04

[Steve Kowalik]

On 08/05/16 08:11, lương hữu tuấn wrote:

Hi,

@Robert: I was successful to update the kernel without change the image.


But that was Robert's point entirely. Installing the kernel will work
fine, but it does not get you running that kernel -- also like Robert
said, you need to change the image to run a different kernel than what
it has installed.

--
Steve
"Stop breathing down my neck!"
"My breathing is merely a simulation."
"So is my neck! Stop it anyway."
 - EMH vs EMH, USS Prometheus

__
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] [TripleO] Proposing Ian Wienand as core reviewer on diskimage-builder

[Steve Kowalik]

On 04/11/15 02:25, Gregory Haynes wrote:
> Current cores - Please respond with any approvals/objections by next Friday
> (November 13th).

+1 from me as well.

-- 
Steve
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver."
 - Daniel Pead

__
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] [packaging] Adding packaging as an OpenStack project

[Steve Kowalik]

On 29/05/15 06:41, Haïkel wrote:
> Here's the main script to rebuild a RPM package.
> https://github.com/openstack-packages/delorean/blob/master/scripts/build_rpm.sh
> 
> The script basically uses rpmbuild to build packages, we could have a
> build_deb.sh that uses
> sbuild and add dockerfiles for the Debian/Ubuntu supported releases.

I have a preliminary patch locally that adds support for building for
both Debian and Ubuntu. I will be applying some polish next week and
then working with the Delorean guys to get it landed.

-- 
Steve
Oh, in case you got covered in that Repulsion Gel, here's some advice
the lab boys gave me: [paper rustling] DO NOT get covered in the
Repulsion Gel.
 - Cave Johnson, CEO of Aperture Science

__
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] [TripleO] nominating James Polley for tripleo-core

[Steve Kowalik]

On 15/01/15 07:14, Clint Byrum wrote:

Hello! It has been a while since we expanded our review team. The
numbers aren't easy to read with recent dips caused by the summit and
holidays. However, I believe James has demonstrated superb review skills
and a commitment to the project that shows broad awareness of the
project.


Very well deserved. +1!

--
Steve
In the beginning was the word, and the word was content-type: text/plain

__
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] How do the CI clouds work?

[Steve Kowalik]

Hai,

I am finding myself at a loss at explaining how the CI clouds that run
the tripleo jobs work from end-to-end. I am clear that we have a tripleo
deployment running on those racks, with a seed, a HA undercloud and
overcloud, but then I'm left with a number of questions, such as:

How do we run the testenv images on the overcloud?

How do the testenv images interact with the nova-compute machines in
the overcloud?

Are the machines running the testenv images meant to be long-running,
or are they recycled after n number of runs?

Cheers,
-- 
Steve
In the beginning was the word, and the word was content-type: text/plain

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [diskimage-builder] ramdisk-image-create fails for creating Centos/rhel images.

[Steve Kowalik]

On 11/12/14 17:51, Harshada Kakad wrote:
> I am trying to build Centos/rhel image for baremetal deployment using
> ramdisk-image-create. I am using my build host as CentOS release 6.5
> (Final).
> It fails saying no busybox available.

The 'ramdisk' element in diskimage-builder requires busybox, which
CentOS/RHEL do not ship. You need to add '--ramdisk-element
dracut-ramdisk' to your command line.

-- 
Steve
In the beginning was the word, and the word was content-type: text/plain

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO] Do we want to remove Nova-bm support?

[Steve Kowalik]

Hi all,

I'm becoming increasingly concerned about all of the code paths
in tripleo-incubator that check $USE_IRONIC -eq 0 -- that is, use
nova-baremetal rather than Ironic. We do not check nova-bm support in
CI, haven't for at least a month, and I'm concerned that parts of it
may be slowly bit-rotting.

I think our documentation is fairly clear that nova-baremetal is
deprecated and Ironic is the way forward, and I know it flies in the
face of backwards-compatibility, but do we want to bite the bullet and
remove nova-bm support?

Cheers,
-- 
Steve
Oh, in case you got covered in that Repulsion Gel, here's some advice
the lab boys gave me: [paper rustling] DO NOT get covered in the
Repulsion Gel.
 - Cave Johnson, CEO of Aperture Science

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [diskimage-builder] Tracing levels for scripts (119023)

[Steve Kowalik]

On 02/12/14 12:27, Ian Wienand wrote:
> - pretty sure SHELLOPTS doesn't survive sudo, which might add another
>   layer of complication for users

sudo is well-known to strip out all but a well-defined list of
environment variables when you use it. sudo -E turns that off,
but the configuration can still prohibit certain variables from
propagating.

Cheers,
-- 
Steve
"Why does everyone say 'Relax' when they're about to do something terrible?"
 - Ensign Harry Kim, USS Voyager

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO] Removing nova-bm support within os-cloud-config

[Steve Kowalik]

With the move to removing nova-baremetal, I'm concerned that portions
of os-cloud-config will break once python-novaclient has released with
the bits of the nova-baremetal gone -- import errors, and such like.

I'm also concerned about backward compatibility -- in that we can't
really remove the functionality, because it will break that
compatibility. A further concern is that because nova-baremetal is no
longer checked in CI, code paths may bitrot.

Should we pony up and remove support for talking to nova-baremetal in
os-cloud-config? Or any other suggestions?

-- 
Steve
If it (dieting) was like a real time strategy game, I'd have loaded a
save game from ten years ago.
 - Greg, Columbia Internet

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] add cyclomatic complexity check to pep8 target

[Steve Kowalik]

On 17/10/14 15:23, Angus Salkeld wrote:
> Thanks for that, I mostly copied your patch for Heat:
> https://review.openstack.org/#/c/129126/
> 
> I wish it would print out the value for all the modules tho', that is
> what is nice about radon.

It's a little horrible, but we can do the same thing:

(pep8)steven@undermined:~/openstack/openstack/heat% flake8
--max-complexity 0 | grep 'is too complex' | sort -k 2 -rn -t '(' | head
./heat/engine/stack.py:809:1: C901 'Stack.delete' is too complex (28)
./heat/tests/v1_1/fakes.py:240:1: C901
'FakeHTTPClient.post_servers_1234_action' is too complex (24)
./heat/engine/resources/server.py:738:1: C901 'Server.handle_update' is
too complex (23)
./doc/source/conf.py:62:1: C901 'write_autodoc_index' is too complex (18)
./heat/engine/stack.py:701:1: C901 'Stack.update_task' is too complex (17)
./heat/engine/resources/instance.py:709:1: C901 'Instance.handle_update'
is too complex (17)
./heat/engine/rsrc_defn.py:340:1: C901 'ResourceDefinition.__getitem__'
is too complex (16)
./heat/engine/resources/random_string.py:175:1: C901
'RandomString._generate_random_string' is too complex (16)
./heat/api/cfn/v1/stacks.py:277:1: C901
'StackController.create_or_update' is too complex (16)
./heat/engine/watchrule.py:358:1: C901 'rule_can_use_sample' is too
complex (15)

Cheers,
-- 
Steve
Oh, in case you got covered in that Repulsion Gel, here's some advice
the lab boys gave me: [paper rustling] DO NOT get covered in the
Repulsion Gel.
 - Cave Johnson, CEO of Aperture Science

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] a need to assert user ownership in preserved state

[Steve Kowalik]

On 02/10/14 12:26, Mike Spreitzer wrote:
> I do not understand the problem statement. Unfortunately, I am not
> familiar with image based updates using TripleO.  What is updating what?
>  If the UIDs are not asserted, what UIDs shift by one?  Is this because
> some files keep owner UID while the some UID=name binding in /etc/passwd
> changes? Or the other way around?  Why would there be a change in either?
> 
> If there is no short answer, don't worry about it.

You build one image, which creates a 'ceilometer' user with UID 1001,
and deploy that to your cloud.

You then build a new image to deploy to your cloud, and due to element
ordering (or something else), the 'cinder' user now has UID 1001. When
you switch to this image, /mnt/state/var/lib/ceilometer is now owned by
cinder.

Cheers,
-- 
Steve
If it (dieting) was like a real time strategy game, I'd have loaded a
save game from ten years ago.
 - Greg, Columbia Internet

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] Propose adding StevenK to core reviewers

[Steve Kowalik]

On 19/09/14 12:22, Robert Collins wrote:
> So we've clearly got a majority support :) - Steve, you up for the challenge?

"I solemnly swear I am up to no go..." Wait, that isn't the quote I'm
after. :-)

I'm delighted to say I'm up for and welcome the challenge.

Cheers,
-- 
Steve
Wrong is endian little that knows everyone but.
 - Sam Hocevar

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO][Ironic] Unique way to get a registered machine?

[Steve Kowalik]

On 22/08/14 17:35, Chris Jones wrote:

Hi

When register-nodes blows up, is the error we get from Ironic sufficiently 
unique that we can just consume it and move on?

I'm all for making the API more powerful wrt inspecting the current setup, but 
I also like idempotency :)


If the master nodes list changes, because say you add a second NIC, and 
up the amount of RAM for a few of your nodes, we then want to update 
those details in the baremetal service, rather than skipping those nodes 
since they are already registered.



Cheers,
--
Chris Jones


On 22 Aug 2014, at 07:32, Steve Kowalik  wrote:

Hi,

TripleO has a bridging script we use to register nodes with a baremetal service (eg: 
Ironic or Nova-bm), called "register-nodes", which given a list of node 
descriptions (in JSON), will register them with the appropriate baremetal service.

At the moment, if you run register-nodes a second time with the same list 
of nodes, it will happily try and register them and then blow up when Ironic or 
Nova-bm returns an error. If operators are going to update their master list of 
nodes to add or remove machines and then run register-nodes again, we need a 
way to skip registering nodes that are already -- except that I don't really 
want to extract out the UUID of the registered nodes, because that puts an onus 
on the operators to make sure that the UUID is listed in the master list, and 
that would be mean requiring manual data entry, or some way to get that data 
back out in the tool they use to manage their master list, which may not even 
have an API. Because our intent is for this bridge between an operators master 
list, and a baremetal service, the intent is for this to run again and again 
when changes happen.

This means we need a way to uniquely identify the machines in the list so 
we can tell if they are already registered.

For the pxe_ssh driver, this means the set of MAC addresses must intersect.

For other drivers, we think that the pm_address for each machine will be 
unique. Would it be possible add some advice to that effect to Ironic's driver 
API?

Cheers,
--
Steve
"Stop breathing down my neck!"
"My breathing is merely a simulation."
"So is my neck! Stop it anyway."
 - EMH vs EMH, USS Prometheus

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




--
Steve
In the beginning was the word, and the word was content-type: text/plain

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO][Ironic] Unique way to get a registered machine?

[Steve Kowalik]

Hi,

	TripleO has a bridging script we use to register nodes with a baremetal 
service (eg: Ironic or Nova-bm), called "register-nodes", which given a 
list of node descriptions (in JSON), will register them with the 
appropriate baremetal service.


	At the moment, if you run register-nodes a second time with the same 
list of nodes, it will happily try and register them and then blow up 
when Ironic or Nova-bm returns an error. If operators are going to 
update their master list of nodes to add or remove machines and then run 
register-nodes again, we need a way to skip registering nodes that are 
already -- except that I don't really want to extract out the UUID of 
the registered nodes, because that puts an onus on the operators to make 
sure that the UUID is listed in the master list, and that would be mean 
requiring manual data entry, or some way to get that data back out in 
the tool they use to manage their master list, which may not even have 
an API. Because our intent is for this bridge between an operators 
master list, and a baremetal service, the intent is for this to run 
again and again when changes happen.


	This means we need a way to uniquely identify the machines in the list 
so we can tell if they are already registered.


For the pxe_ssh driver, this means the set of MAC addresses must 
intersect.

	For other drivers, we think that the pm_address for each machine will 
be unique. Would it be possible add some advice to that effect to 
Ironic's driver API?


Cheers,
--
Steve
"Stop breathing down my neck!"
"My breathing is merely a simulation."
"So is my neck! Stop it anyway."
 - EMH vs EMH, USS Prometheus

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO] Python 3 support in os-*-config

[Steve Kowalik]

Hai,

I've been poking at Python 3 support in os-*-config recently, and
here's what is going on with it:

 * os-apply-config
   This one looks to be the hardest one to port. Multiple test failures,
hard coded use of '#!/usr/bin/env python' which is unhappy in a only
Python 3 environment, map() changes, byte changes ...

 * os-cloud-config
   I have a patch to fix current Python 3 issues up
(https://review.openstack.org/111606), and then my plan is to add Python
3 jobs to check *and* gate, so in-flight patches may need to watch out
for that soon.

 * os-collect-config
   This needs six sprinkled throughout it due to URL parsing, and I need
to work out what to do WRT absolute importing due to:
  File "./os_collect_config/collect.py", line 25, in 
from openstack.common import log
ImportError: No module named 'openstack'

 * os-net-config
   I know this isn't really a thing yet, but I also have yet to look
into it's Python 3 support.

 * os-refresh-config
   This has Python 3 jobs running in check and gate. Does anyone have a
small fix to test them out, the last code change that landed in
os-refresh-config was mid July.

Thanks,
-- 
Steve
"I hate temporal mechanics!"
 - Chief Miles O'Brien, Deep Space Nine

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Tuskar] Not able to set up the stack

[Steve Kowalik]

On 15/07/14 15:26, Peeyush Gupta wrote:
> I have been trying to set up TripleO. To do that, i first installed
> ironic with devstack. So, I have three baremetal node. Then I went
> on to install tuskar and tuskar-ui using their respective installation
> guides
> i.e. https://github.com/openstack/tuskar/blob/master/doc/source/INSTALL.rst
> and http://tuskar-ui.readthedocs.org/en/latest/install.html.
> 
> Now, I am running tuskar-ui, I get the error as : The stack (overcloud)
> could
> not be found.
> 
> Any ideas about how to resolve this?

Tuskar is expecting a TripleO stack, not devstack below it. You should
be running it on top of a devtest environment, see
http://docs.openstack.org/developer/tripleo-incubator/devtest.html

Cheers,
-- 
Steve
"I'm a doctor, not a doorstop!"
 - EMH, USS Enterprise

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] [ironic] Multiple VM sizes for devtest

[Steve Kowalik]

On 15/07/14 11:12, Steve Kowalik wrote:
> Flavors as of right now will only create a flavor that matches the first
> nodes specification, but there is work underway already to fix that up
> -- the first step of which is to move to the create-nodes provided by
> os-cloud-config.

That should be register-nodes, not create-nodes. :-(

-- 
Steve
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver."
 - Daniel Pead

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tripleo] [ironic] Multiple VM sizes for devtest

[Steve Kowalik]

On 15/07/14 05:39, Matthew Gilliard wrote:
>   In my head, a rough plan is: allow a user to provide a file detailing
> the specs of the VMs they want.  (If it's not supplied we can fallback
> to the current behaviour).  Nodes are created and given "roles"
> according to the contents of that file, and flavors are created to
> match.  When the UC and OC VMs are booted, the flavor appropriate to the
> "role" is used.  As you can imagine, most parts of devtest would need
> some changes - I guess around a half-dozen individual patchsets might do
> it, maybe more.
> 
>   So, I put this email out to see what people's reactions are.  If they
> are generally positive I think it would be worth a tripleo-spec to put a
> bit more detail together.  What do you think?

You can already specify a list to use as nodes (see the --nodes option
from devtest.sh) for devtest, but this is commonly used to describe
actual baremetal machines that you want devtest to use. If the VMs
already exist, I don't foresee any issue with specifying them to a
devtest run in the same way.

Flavors as of right now will only create a flavor that matches the first
nodes specification, but there is work underway already to fix that up
-- the first step of which is to move to the create-nodes provided by
os-cloud-config.

Cheers,
-- 
Steve
Wrong is endian little that knows everyone but.
 - Sam Hocevar

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack] is tenant-id in network API?

[Steve Kowalik]

On 07/07/14 13:56, Anne Gentle wrote:
> Please check to see if this patch fixes the issue:
> 
> https://review.openstack.org/1050
> 
That's a patch (actually against quantum, which is amusing) from 2011, I
think you're missing a few numbers at the end. :-)

-- 
Steve
C offers you enough rope to hang yourself.
C++ offers a fully equipped firing squad, a last cigarette and
a blindfold.
 - Erik de Castro Lopo

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Jenkins] [Cinder] InvocationError in gate-cinder-python26 & python27

[Steve Kowalik]

On 30/06/14 16:37, Amit Das wrote:
> I have been facing below issues at gate-cinder-python26 &
> gate-cinder-python27 after uploading my patch.
> 
> I assume this to be an infrastructure issue than an issue with my patch.
> Can someone please confirm ?
> 
> .
> 2014-06-30 05:41:57.704 | check_uptodate.sh: cinder.conf.sample is not
> up to date.

This usually means that Oslo (the common libraries used by many
projects) has added an configuration option. It's in fact a problem with
cinder, in that they need to make sure the sample configuration file is
up to date, but it will affect all patches until it is fixed. I'm sure
it will get sorted out quickly.

Personally, I think generating and comparing a sample config every build
is daft, and a sample configuration should be generated during sdist or
something.

Cheers,
-- 
Steve
"Stop breathing down my neck!"
"My breathing is merely a simulation."
"So is my neck! Stop it anyway."
 - EMH vs EMH, USS Prometheus

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [hacking] rules for removal

[Steve Kowalik]

On 25/06/14 07:26, Mark McLoughlin wrote:
> There's two sides to this coin - concern about alienating
> non-english-as-a-first-language speakers who feel undervalued because
> their language is nitpicked to death and concern about alienating
> english-as-a-first-language speakers who struggle to understand unclear
> or incorrect language.
> 
> Obviously there's a balance to be struck there and different people will
> judge that differently, but I'm personally far more concerned about the
> former rather than the latter case.
> 
> I expect many beyond the english-as-a-first-language world are pretty
> used to dealing with imperfect language but aren't so delighted with
> being constantly reminded that their use language is imperfect.

Just to throw my two cents into the ring, when I comment about language
use in a review, I will almost always include suggested wording in full.
If I can't come to a decision about if my wording is better, than I
don't comment on it.

Cheers,
-- 
Steve
"I'm a doctor, not a doorstop!"
 - EMH, USS Enterprise

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] dib-utils Release Question

[Steve Kowalik]

On 24/06/14 06:31, Jay Dobies wrote:
> I finished the releases for all of our existing projects and after
> poking around tarballs.openstack.org and pypi, it looks like they built
> successfully. Yay me \o/
> 
> However, it doesn't look like dib-utils build worked. I don't see it
> listed on tarballs.openstack.org. It was the first release for that
> project, but I didn't take any extra steps (I just followed the
> instructions on the releases wiki and set it to version 0.0.1).
> 
> I saw the build for it appear in zuul but I'm not sure how to go back
> and view the results of a build once it disappears off the main page.
> 
> Can someone with experience releasing a new project offer me any insight?

\o/

I've been dealing with releases of new projects from the os-cloud-config
side recently, so let's see.

dib-utils has a post job of dib-utils-branch-tarball, so the job does
exist, as you pointed out, but it doesn't hurt to double check.

The object the tag points to is commit
45b7cf44bc939ef08afc6b1cb1d855e0a85710ad, so logs can be found at
http://logs.openstack.org/45/45b7cf44bc939ef08afc6b1cb1d855e0a85710ad

And from the log a few levels deep at the above URL, we see:

2014-06-16 07:17:13.122 | + tox -evenv python setup.py sdist
2014-06-16 07:17:13.199 | ERROR: toxini file 'tox.ini' not found
2014-06-16 07:17:13.503 | Build step 'Execute shell' marked build as failure

Since it's not a Python project, no tarball or pypi upload.

Cheers,
-- 
Steve
"I'm a doctor, not a doorstop!"
 - EMH, USS Enterprise

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO][Tuskar] Feedback on init-keystone spec

[Steve Kowalik]

Hi,

	I'm looking at moving init-keystone from tripleo-incubator to 
os-cloud-config, and I've drafted a spec at 
https://etherpad.openstack.org/p/tripleo-init-keystone-os-cloud-config .


Feedback welcome.

Cheers,
--
Steve
"I hate temporal mechanics!"
 - Chief Miles O'Brien, Deep Space Nine

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack][nova][Neutron] Launch VM with multiple Ethernet interfaces with I.P. of single subnet.

[Steve Kowalik]

On 17/04/14 14:20, Aaron Rosen wrote:
> You can do it with ip aliasing and use one interface: 
> 
> ifconfig eth0 10.0.0.22/24 
> ifconfig eth0:1 10.0.0.23/24 
> ifconfig eth0:2 10.0.0.24/24 

The 'ip' command can also do it.

ip address add 10.0.0.23/24 dev eth0
ip address add 10.0.0.24/24 dev eth0

> 
> 2: eth0:  mtu 1500 qdisc mq state
> DOWN qlen 1000
> link/ether 40:6c:8f:1a:a9:31 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.22/24  brd 10.0.0.255 scope global eth0
>valid_lft forever preferred_lft forever
> inet 10.0.0.23/24  brd 10.0.0.255 scope global
> secondary eth0:1
>valid_lft forever preferred_lft forever
> inet 10.0.0.24/24  brd 10.0.0.255 scope global
> secondary eth0:2
>valid_lft forever preferred_lft forever
> 
> 
> 
> On Wed, Apr 16, 2014 at 8:53 PM, Kevin Benton  > wrote:
> 
> Web server running multiple SSL sites that wants to be compatible
> with clients that don't support the SNI extension. There is no way
> for a server to get multiple IP addresses on the same interface is
> there?
> 
> 
> On Wed, Apr 16, 2014 at 5:50 PM, Aaron Rosen  > wrote:
> 
> This is true. Several people have asked this same question over
> the years though I've yet to hear a use case why one really need
> to do this. Do you have one? 
> 
> 
> On Wed, Apr 16, 2014 at 3:12 PM, Ronak Shah
> mailto:ro...@nuagenetworks.net>> wrote:
> 
> Hi Vikash,
> Currently this is not supported. the NIC not only needs to
> be in different subnet, they have to be in different network
> as well (container for the subnet)
> 
> Thanks
> Ronak
> 
> On Wed, Apr 16, 2014 at 3:51 AM, Vikash Kumar
>  > wrote:
> 
> *With 'interfaces' I mean 'nics' of VM*.
> 
> 
> On Wed, Apr 16, 2014 at 4:18 PM, Vikash Kumar
>  > wrote:
> 
> Hi,
> 
>  I want to launch one VM which will have two
> Ethernet interfaces with IP of single subnet. Is
> this supported now in openstack ? Any suggestion ?
> 
> 
> Thanx
> 
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> 
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> -- 
> Kevin Benton
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


-- 
Steve
"I'm a doctor, not a doorstop!"
 - EMH, USS Enterprise

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat] Standing down as PTL

[Steve Kowalik]

On 03/04/14 16:03, Monty Taylor wrote:
> All hail the Mooball release.
> 
> Now we just have to find a city that's in a state or country with a
> placename of "Mooball" - that shouldn't be too hard ...

http://en.wikipedia.org/wiki/Mooball,_New_South_Wales

> On 04/02/2014 08:20 PM, Qiming Teng wrote:
>> Let's vote for the K, L, M release names now. :)
>>
>> Thanks, Steve.
>>
>> On Mon, Mar 31, 2014 at 11:22:49AM +1300, Steve Baker wrote:
>>> I don't intend to run for PTL for the Juno cycle; thankfully there are
>>> many Heat developers who would do a great job.
>>>
>>> Hopefully this wasn't a one-off though. I may run again for Kilmacow,
>>> Lacrosse or Mooball.
>>>
>>> cheers
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-- 
Steve
Wrong is endian little that knows everyone but.
 - Sam Hocevar

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] Alternating meeting time for more TZ friendliness

[Steve Kowalik]

On 19/03/14 06:57, James Slagle wrote:
> Our current meeting time is Tuesdays at 19:00 UTC.  I think this works
> ok for most folks in and around North America.
> 
> It was proposed during today's meeting to see if there is interest is
> an alternating meeting time every other week so that we can be a bit
> more friendly to those folks that currently can't attend.
> If that interests you, speak up :).

Also speaking up.

It gets a little difficult if we want the meeting time to cover Europe,
North America, New Zealand and Australia, since that's effectively the
entire world. I would prefer a little later than 0700, but I understand
that another hour might push it in another timezone to  or 0100.

Cheers,
-- 
Steve
C offers you enough rope to hang yourself.
C++ offers a fully equipped firing squad, a last cigarette and
a blindfold.
 - Erik de Castro Lopo

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] testr help

[Steve Kowalik]

On 07/03/14 12:56, John Dennis wrote:

Question: How do you list just the failing tests? I don't want to see
the contents of the logging data stored under the pythonlogging: key.
Ideally I'd like to see the name of the test, what the failure was, and
possibly the associated stacktrace. Should be simple right? But I can't
figure it out.


"testr failing" or "testr failing --list". See also "testr run --failing".

Cheers,
--
Steve
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver."
 - Daniel Pead

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Sent the first batch of invitations to Atlanta's Summit

[Steve Kowalik]

On 18/02/14 11:26, Robert Collins wrote:
> NVM. Found the nicely styled small text in low contrast colour.
> 
> /me headdesks

I found it completely non-obvious too, and had to go back and look for
the link. If the promotion code text box was always visible with the
Apply button grayed out when the text box is empty, I think that would help.

Cheers,
-- 
Steve
Oh, in case you got covered in that Repulsion Gel, here's some advice
the lab boys gave me: [paper rustling] DO NOT get covered in the
Repulsion Gel.
 - Cave Johnson, CEO of Aperture Science


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev