Re: [Openstack] use of internal endpoint url instead of public url

[Patrick Petit]

On Feb 13, 2013, at 6:14 PM, Mac Innes, Kiall wrote:

 On 13/02/13 17:07, Scott Devoid wrote:
 We're also lacking support for setting --endpoint-type in keystone. In
 my case, it's trying to use adminURL when publicURL is the only one
 externally reachable.
 
 The keystone client doesn't use the --endpoint-type flag, since you have
 to supply a URL in the first place! Usually via an env var.
 
 Are all of these effectively the same?
 --os-endpoint service-endpoint
 --endpoint-type xURL
 --bypass-url url
 
 No. endpoint-type takes in a type (Either publicURL, internalURL
 or adminURL) and not an actual URL. This type is then used to lookup
 the URL from keystone's catalog.
 

Thank you the clarification!
So, that's what endpoint-type is used for… Sounds obvious once you know it.
I think it would work better if spelled out accordingly in nova help with 
something like:

--endpoint-type endpoint-type
Defaults to env[NOVA_ENDPOINT_TYPE]
Allowed values are:   publicURL (default), 
internalURL and adminURL

--bypass-url bypass-url
Use this API endpoint instead of the Service Catalog's 
default endpoint URLs


 --os-endpoint and --bypass-url appear to be the same thing though..
 
 Thanks,
 Kiall
 


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] use of internal endpoint url instead of public url

[Patrick Petit]

Dear All,

How can I direct nova CLI to use the internal service endpoint URL 
instead of the public one? Same question applies to cinder CLI. I 
managed to find my way through with glance CLI which supports an 
OS_IMAGE_URL environment variable whereas OS_COMPUTE_URL and 
OS_VOLUME_URL seem to have not effect.

Any help would be greatly appreciated.
Thanks
Patrick

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Problems with Fn::Join

[Patrick Petit]

Hi,

We are seeing a new behavior with Fn::Join in user-data block that makes 
our script fail to run. Previous behavior was that no white space nor 
line breaks were inserted after a coma (',') or line ends. But now it's 
inserting white space plus line break after ',' separated elements... Do 
you have any idea why?

Thanks
Patrick

_Exemple_:

Fn::Join:[
 \n,
 [
#!/bin/bash -v,
# Helper function,
function error_exit\n,
{\n,
  /opt/aws/bin/cfn-signal -e 1 -r \$1\ ', { 
Ref : BatchNodeWaitHandle }, '\n,

  exit 1\n,
}\n,

# Flush iptables's default rules,
/sbin/iptables -F,
/sbin/iptables -X,
# prepare for packages install,
yum update -y,
yum upgrade -y,
export http_proxy=ecfrec.frec.bull.fr:8080,
export 
no_proxy=127.0.0.1,localhost,.amg.net.pl,169.254.169.254,10.197.217.62,


/opt/aws/bin/cfn-init -s , { Ref : 
AWS::StackName },

 -r BatchNode ,
 --region , { Ref : AWS::Region },
 || error_exit 'Failed to run cfn-init for 
BatchNode'\n,


rpm -Uvh http://rbel.frameos.org/rbel6;,
#install rubygems,
cd /opt,
tar zxf rubygems-1.8.10.tgz,
cd rubygems-1.8.10,
ruby setup.rb --no-format-executable,
gem install chef --no-ri --no-rdoc,
/opt/aws/bin/cfn-signal -e $? ', { 
Ref:BatchNodeWaitHandle }, '

 ]
  ]

_Results in broken __cfn-userdata script_

#!/bin/bash -v
# Helper function

function error_exit

{

  /opt/aws/bin/cfn-signal -e 1 -r $1 '
http://172.16.1.1:8002/stacks/1a7b8501-e117-4cf8-9838-416446a43fed/resources/BatchNodeWaitHandle
'

  exit 1

}


# Flush iptables's default rules
/sbin/iptables -F
/sbin/iptables -X
# prepare for packages install
yum update -y
yum upgrade -y
export http_proxy=ecfrec.frec.bull.fr:8080
export 
no_proxy=127.0.0.1,localhost,.amg.net.pl,169.254.169.254,10.197.217.62

/opt/aws/bin/cfn-init -s
skeleton
 -r BatchNode
 --region
ap-southeast-1
 || error_exit 'Failed to run cfn-init for BatchNode'
rpm -Uvh http://rbel.frameos.org/rbel6
#install rubygems
cd /opt
tar zxf rubygems-1.8.10.tgz
cd rubygems-1.8.10
ruby setup.rb --no-format-executable
gem install chef --no-ri --no-rdoc
/opt/aws/bin/cfn-signal -e $? '
http://172.16.1.1:8002/stacks/1a7b8501-e117-4cf8-9838-416446a43fed/resources/BatchNodeWaitHandle
'
touch /var/lib/cloud/instance/provision-finished

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Problems with Fn::Join

[Patrick Petit]

Steve,
Yes it does.
Thanks!
Patrick
On 12/14/12 11:22 AM, Steven Hardy wrote:

On Fri, Dec 14, 2012 at 09:57:42AM +0100, Patrick Petit wrote:

Hi,

We are seeing a new behavior with Fn::Join in user-data block that
makes our script fail to run. Previous behavior was that no white
space nor line breaks were inserted after a coma (',') or line ends.
But now it's inserting white space plus line break after ','
separated elements... Do you have any idea why?
Thanks
Patrick

_Exemple_:

Fn::Join:[
  \n,

Here you are specifying \n as the delimiter, so the fields are being
joined by a newline.  If you replace the \n with  then no newline will
be inserted.

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-join.html

HTH,




--
Patrick PETIT
Cloud Computing Lead Architect, Innovative Products
Bull, Architect of an Open World TM
Tél : +33 (0)4 76 29 70 31
Mobile : +33 (0)6 85 22 06 39
http://www.bull.com


___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] Instance no route to host problem

[Patrick Petit]

Ooops... I got it. Thought nova-compute has responsibilities in local
iptables settings.
I guess I was misled by the fact that I have default iptables rules setup
at boot time in my VM which looks like rules defined in security group but
it's just a coincidence.
Thanks
Patrick



2012/12/10 Patrick Petit patrick.michel.pe...@gmail.com

 Hi Lei,

 I could spend some more time looking at my no route to host issue today.
 I could be very well that the iptables on VM is the root of the problem.

 Here is what it looks like.


 *$ sudo iptables -L*
 *Chain INPUT (policy ACCEPT)*
 *target prot opt source   destination *
 *ACCEPT all  --  anywhere anywhere state
 RELATED,ESTABLISHED*
 *ACCEPT icmp --  anywhere anywhere*
 *ACCEPT all  --  anywhere anywhere*
 *ACCEPT tcp  --  anywhere anywhere state NEW
 tcp dpt:ssh*
 *REJECT all  --  anywhere anywhere
 reject-with icmp-host-prohibited*
 *
 *
 *Chain FORWARD (policy ACCEPT)*
 *target prot opt source   destination *
 *REJECT all  --  anywhere anywhere
 reject-with icmp-host-prohibited*
 *
 *
 *Chain OUTPUT (policy ACCEPT)*
 *target prot opt source   destination  *

 I am not unfortunately very familiar with iptables's rules syntax
 Shouldn't ACCEPT all -- anywhere anywhere allow my http traffic to port 80?

 However, running explicitly

 *sudo iptables -A INPUT -p tcp -i eth0 --dport 80 -j ACCEPT*

 Does fix the problem. I can access my instance on port 80.

 But my VM is associated with the default security group in which I added a
 rule to enable http traffic.

 $ nova secgroup-list-rules default
 +-+---+-+---+--+
 | IP Protocol | From Port | To Port | IP Range  | Source Group |
 +-+---+-+---+--+
 | icmp| -1| -1  | 0.0.0.0/0 |  |
 | tcp | 22| 22  | 0.0.0.0/0 |  |
 | tcp | 80| 80  | 0.0.0.0/0 |  |
 +-+---+-+---+--+

 So the big question is why aren't my iptables rules in the VM no setup by
 the security group specs?
 I don't see any error in nova logs on the compute node.

 Any help would be really appreciated.
 Thanks
 Patrick





 2012/12/6 Lei Zhang zhang.lei@gmail.com

 Could you check the iptables in the vm? Whether it drop the packets on
 the port 80


 On Thu, Dec 6, 2012 at 12:29 AM, Patrick Petit 
 patrick.michel.pe...@gmail.com wrote:

 Dear Stackers,

 I am running instance wordpress.WikiServer


  $ nova list

 +--+--+++
 | ID   | Name |
 Status | Networks   |

 +--+--+++
 | 6be47af7-2e29-4b4c-afeb-0a7f760f5970 | test2|
 ACTIVE | xlcloud=172.16.1.6 |
 | 5a4c552f-933c-4a06-8e6f-164176380af5 | wordpress.DatabaseServer |
 ACTIVE | xlcloud=172.16.1.3 |
 | ddb120d9-e1ad-444c-8490-37ecb15f500e | wordpress.WikiServer |
 ACTIVE | xlcloud=172.16.1.4, 10.197.217.131 |

 +--+--+++


 With Security Group setup as:

 $ nova secgroup-list

 +---++
 | Name  | Description
  |

 +---++
 | default   | default
  |

 +---++


 $ nova secgroup-list-rules default
 +-+---+-+---+--+
 | IP Protocol | From Port | To Port | IP Range  | Source Group |
 +-+---+-+---+--+
 | icmp| -1| -1  | 0.0.0.0/0 |  |
 | tcp | 22| 22  | 0.0.0.0/0 |  |
 | tcp | 80| 80  | 0.0.0.0/0 |  |
 +-+---+-+---+--+

 I can ping and ssh through the fix or floating IP without any problem
 (172.16.1.4, 10.197.217.131).
 But HTTP requests on port 80 doesn't go through.
 I get a no route host error message from wget or telnet for example.

 Ex. $ telnet 172.16.1.4 80
 Trying 172.16.1.4...
 telnet: Unable to connect to remote host: No route to host.
 Clearly it's not a routing problem.

 Any idea what the problem could be or hints to debug it.

 Thanks
 Patrick

Re: [Openstack] [ceilometer] Monitoring physical devices

[Patrick Petit]

Folks,
I'd like to add to this that physical server metering shouldn't be treated 
differently in Ceilometer now that bare metal provisioning framework enters 
into Grizzly. Physical servers will just become billable resources much like 
VMs. I am not speaking of physical server monitoring here. Just extending 
Ceilometer agent to also report usage data out of the physical box.
Cheers
Patrick

Envoyé de mon iPad

Le 1 nov. 2012 à 19:13, Julien Danjou jul...@danjou.info a écrit :

 On Thu, Nov 01 2012, Zehnder Toni (zehndton) wrote:
 
 My goal is to offer monitored data to the admin and customers. The admin is
 interested in the utilization of the physical components and the virtual
 machines and the customer is interested to know what his VMs do or can do.
 It would be nice to get the data from a single point. I thought I can
 enhance the Ceilometer compute agent to get this data out. Does this make
 sense or is it better to use another monitoring tool for the physical
 components?
 
 I think the pollster implementation can be done. I wouldn't implement
 this in the compute agent, but probably in some hardware agent, because
 it's likely it would be used in different kinds of environment and not
 only on compute node, i.e. you may also want to meter hardware usage for
 you cinder or glance node anyway.
 
 About the 10 minutes polling interval Doug mentionned, this can be a
 problem indeed, but it's still solvable later and would be easy to solve
 if this in a different agent, since you could change the periodic
 interval for pollster runs to something like 1 or 5 minutes.
 
 -- 
 Julien Danjou
 // Free Software hacker  freelance
 // http://julien.danjou.info
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Docs] Documentation set for Folsom

[Patrick Petit]

Hi There,

Can someone tell me what is current plan regarding the release of the
documentation set for Folsom?
Of particular interest is the admin guide extension covering Quantum.
Thanks
Patrick
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

[Patrick Petit]

Hi Don,

I added a comment in https://bugs.launchpad.net/nova/+bug/1039386 regarding
your point.
Best regards,
Patrick

2012/8/24 Dugger, Donald D donald.d.dug...@intel.com

  Patrick-

 ** **

 We’ve enhanced `nova-manage’ to manipulate the `extra_specs’ entries, c.f.
 https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value,
   You can add an `extra_specs’ key/value pair to a flavor with the command:
 

 ** **

 nova-manage instance_type add_key m1.humongous cpu_type
 itanium

 ** **

 And delete a key/value pair with the command:

 ** **

 nova-manage instance_type del_key m1.humongous cpu_type***
 *

 ** **

 We’re in the process of enhancing `python-novaclient’ and Horizon with
 similar capabilities and hope to have them ready for the Folsom release.**
 **

 ** **

 Currently, there’s no hook to set `extra_specs’ through the `nova.conf’
 file, the mechanism is to dynamically add the `extra_specs’ key/values
 after the administrator has created a flavor.

 ** **

 Currently, the keys are completely free form but there are some issues
 with that so that should change.  Checkout the bug:

 ** **

 https://bugs.launchpad.net/nova/+bug/1039386

 ** **

 Based upon that bug we need to put some sort of scope on the keys to
 indicate which components a key applies to. I’m in favor of adding a new
 column to the `extra_specs’ table that would explicitly set the scope but
 an alternative would be to encode the scope into the key itself, something
 like `TrustedFilter:trust’ to indicate that  the `trust’ key only applies
 to the `TrustedFilter’ scheduler component.  Feel free to chime in on the
 BZ entry on how to specify the scope, once we decide on how to deal with
 this I’ll create a patch to handle it.

 ** **

 --

 Don Dugger

 Censeo Toto nos in Kansa esse decisse. - D. Gale

 Ph: 303/443-3786

 ** **

 *From:* 
 openstack-bounces+donald.d.dugger=intel@lists.launchpad.net[mailto:
 openstack-bounces+donald.d.dugger=intel@lists.launchpad.net] *On
 Behalf Of *Patrick Petit
 *Sent:* Friday, August 24, 2012 7:13 AM
 *To:* openstack@lists.launchpad.net (openstack@lists.launchpad.net)
 *Subject:* [Openstack] [Nova] Instance Type Extra Specs clarifications

 ** **

 Hi,

 ** **

 Could someone give a practical overview of how configuring and using the
 instance type extra specs extension capability introduced in Folsom?

 ** **

 If how extending an instance type is relatively clear.

 ** **

 Eg.: #nova-manage instance_type set_key --name=my.instancetype --key
 cpu_arch --value 's== x86_64' 

 ** **

 The principles of capability advertising is less clearer. Is it assumed
 that the key/value pairs are always declared statically as flags in
 nova.conf of the compute node, or can they be generated dynamically and if
 so, who would that be? And also, are the keys completely free form strings
 or strings that are known (reserved) by Nova?

 ** **

 Thanks in advance for clarifying this.

 ** **

 Patrick




-- 
*Give me a place to stand, and I shall move the earth with a lever*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Nova] Instance Type Extra Specs clarifications

[Patrick Petit]

Hi,

Could someone give a practical overview of how configuring and using the
instance type extra specs extension capability introduced in Folsom?

If how extending an instance type is relatively clear.

Eg.: #nova-manage instance_type set_key --name=my.instancetype --key
cpu_arch --value 's== x86_64'

The principles of capability advertising is less clearer. Is it assumed
that the key/value pairs are always declared statically as flags in
nova.conf of the compute node, or can they be generated dynamically and if
so, who would that be? And also, are the keys completely free form strings
or strings that are known (reserved) by Nova?

Thanks in advance for clarifying this.

Patrick
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Nova] Instance Type Extra Specs clarifications

[Patrick Petit]

Hi Joseph and All,

You are pointing the root cause of my question. The question is about how to 
specify capabilities for a compute node so that they can be compared with the 
extra specs. I think how to define extra specs in a flavor is clear enough.

So, some capabilities are standard and are generated dynamically. Others are 
not known or not captured by the system and so not standard (yet), like the 
GPUs, and therefore must be specified somehow. Today, the somehow, as I 
understand things, is to add key/value pairs in nova.conf when/if it is 
supported.

I wanted to make sure i understand the basic principals.

Now, this in my opinion poses couple problems and/or call for additional 
questions:

What is the naming convention to add capabilities in nova.conf? I would suppose 
that any key/value pair cannot be taken for a capability.

How to avoid name clashing with standard capability? At the very least one 
should have an option to print them out (in nova-manage?). Even a simple 
written list would be helpful.

But, are we really comfortable with the idea to define static capabilities in 
nova.conf? that's putting a lot of burden on config management. Also, not 
standard doesn't imply static.

We can certainly live we that for now, But eventually, i think we'll need some 
sort of an extension mechanism so that providers can generate whatever 
capabilities they want using their own plugin? Note that capabilities could be 
software related too.

What do you think?
Best,
Patrick

Envoyé de mon iPad

Le 24 août 2012 à 18:38, Joseph Suh j...@isi.edu a écrit :

 Patrick,
 
 Once a new item (key and value pair) is added to the capabilities, it can be 
 compared against extra_specs. The extra_specs can be populated in 
 instance_type_extra_specs table. The items in the extra_specs can start with 
 one of the keywords for operations such as = and s==. For example, if 
 ngpus: 4 is populated in capability, extra_specs of = 2 will choose the 
 host. If the extra_specs is = 5, the host will not be chosen. If no 
 keyword is found at the beginning of the extra_specs (with the latest change 
 in upstream code), the given string is directly compared with capability. For 
 example, if fpu is given as extra_specs, the capability must be fpu to be 
 selected.
 
 If more clarification is needed, please let us know.
 
 Thanks,
 
 Joseph
 
 - Original Message -
 From: David Kang dk...@isi.edu
 To: Patrick Petit patrick.michel.pe...@gmail.com
 Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net) 
 openstack@lists.launchpad.net
 Sent: Friday, August 24, 2012 11:34:11 AM
 Subject: Re: [Openstack] [Nova] Instance Type Extra Specs clarifications
 
 
 Parick,
 
 We are using the feature in Bare-metal machine provisioning.
 Some keys are automatically generated by nova-compute.
 For example, hypervisor_type, hypervisor_version, etc. fields are 
 automatically
 put into capabilities by nova-compute (in the case of libvirt).
 So, you don't need to specify that.
 But, if you want to add custom fields, you should put them into nova.conf 
 file of 
 the nova-compute node.
 
 Since the new key are put into 'capabilities', 
 the new key must be different from any other keys in the 'capabilities'.
 If that uniqueness is enforced, it can be any string, I believe.
 
 Thanks,
 David
 
 --
 Dr. Dong-In David Kang
 Computer Scientist
 USC/ISI
 
 - Original Message -
 Hi,
 
 
 Could someone give a practical overview of how configuring and using
 the instance type extra specs extension capability introduced in
 Folsom?
 
 
 If how extending an instance type is relatively clear.
 
 
 Eg.: #nova-manage instance_type set_key --name=my.instancetype --key
 cpu_arch --value 's== x86_64'
 
 
 The principles of capability advertising is less clearer. Is it
 assumed that the key/value pairs are always declared statically as
 flags in nova.conf of the compute node, or can they be generated
 dynamically and if so, who would that be? And also, are the keys
 completely free form strings or strings that are known (reserved) by
 Nova?
 
 
 Thanks in advance for clarifying this.
 
 
 Patrick
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help : https://help.launchpad.net/ListHelp
 
 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Nova] Create multiple instances in one request

[Patrick Petit]

Hi,
So, if I paraphrase correctly what is meant out of the stacker jargon.

min_count and max_count doc will go in the API doc as an extension item
once the DisableServerExtension cleanup is done. Right?

However, the original question was about the *num_instances* property of
the RPC request spec. I do not see a direct relationship with min_count and
max_count. So, is num_instances another undocumented API extension
parameter or something else?

I can see also that DisableServerExtensions proposal mentions a *reservation_id
*parameter... Can someone explain what it is ? Is it to support server
reservation like in AWS EC2? And so, would a user be able to create a
reservation (that is, not to actually create the reserve servers but to
reserve the) with say additional min_count max_count parameters in the
request. The reservation would fail if min_count cannot be honored by
OpenStack. If the reservation can be honored, would return a reservation_id
along with a value between min_count and max_count. Is this a correct
understanding of the behavior or complete speculation?

Thanks for shedding some light on this

Best regards,
Patrick


2012/8/7 Anne Gentle a...@openstack.org

 These were documented but then pulled out because min_count and
 max_count are not to spec.

 We are now working on a cleanup effort described at
 http://wiki.openstack.org/DisableServerExtensions.

 It seems the log from the last Nova meeting where this was discussed
 is gathered together with the QA team meeting due to the meetbot not
 being turned off between meetings.

 The log is here, scroll to the bottom to read.

 http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-17.00.log.html

 Hope this is helpful - though cleanup will be the most helpful, please
 feel free to join in the effort. :)
 Anne

 On Tue, Aug 7, 2012 at 1:13 PM, David Kranz david.kr...@qrclab.com
 wrote:
  It is a little strange but the following seems to be true.
 
  1. The nova HTTP API has a max_count and min_count that go in the request
  dictionary.
  2. This is not documented.
  3. The novaclient python api create function has these arguments.
  4. The novaclient cli does not have them, or at least they are not
  documented by 'nova help boot'.
 
  Beats me why this is the case...
 
   -David
 
 
  On 8/7/2012 1:47 PM, Patrick Petit wrote:
 
  Dear All,
 
  Looking into the details of the request_spec part of a RPC message
 ensuing a
  nova boot command.
  There is a 'num_instances' : 1 property that implies the value could be
  different than one (default) even though there is no cardinality
 parameter
  in nova boot nor in the API (unless I missed something big). So, I am
  curious to know: why is it there if we cannot create more than one
 instance
  at a time through the API, but more importantly is there a (secret) way
 to
  set that value different than 1 to tell the scheduler please create
  multiple instances of that type.
  Thanks in advance
  Patrick
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 
 
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp
 

 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
*Give me a place to stand, and I shall move the earth with a lever*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Nova] Create multiple instances in one request

[Patrick Petit]

Dear All,

Looking into the details of the request_spec part of a RPC message ensuing
a nova boot command.
There is a 'num_instances' : 1 property that implies the value could be
different than one (default) even though there is no cardinality parameter
in nova boot nor in the API (unless I missed something big). So, I am
curious to know: why is it there if we cannot create more than one instance
at a time through the API, but more importantly is there a (secret) way to
set that value different than 1 to tell the scheduler please create
multiple instances of that type.
Thanks in advance
Patrick
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [HPC] BoF at SC12

[Patrick Petit]

Hi Lorin,
Like every year there is a Bull delegation participating to this event.
So we will surely attend your session if you make one.
Would be a good opportunity to meet and discuss joining efforts.
Best regards,
Patrick


2012/7/23 Lorin Hochstein lo...@nimbisservices.com

 On Jul 6, 2012, at 1:28 PM, John Paul Walters wrote:

 I'm strongly considering putting together a proposal for a BoF (birds of a
 feather) session at this year's Supercomputing in Salt Lake City.  For
 those of you who are likely to attend, is anyone else interested?  It's not
 a huge amount of time invested on my end to put together the proposal, but
 I'd like to gauge the community interest before doing so.  I would likely
 broaden things a bit from being exclusively Openstack and instead turn it
 into more of an HPC in the Cloud session so that we could, perhaps, take
 some input from other HPC cloud projects.   The submissions are due July
 31, so we've got a little bit of time, but not too much.  Anyone else
 interested?

 best,
 JP


 JP:

 I think this was a great idea, we were thinking about proposing this if
 nobody else did. I would suggest making it OpenStack-specific, since there
 was  an HPC in the Cloud BoF last year (
 http://sc11.supercomputing.org/schedule/event_detail.php?evid=bof140),
 and they'll probably re-apply this year as well. I think we can get
 critical mass for an OpenStack BoF.

 Along these lines: Chris Hoge from U. Oregon gave a talk last week at
 OSCON about their use of OpenStack on HPC
 http://www.oscon.com/oscon2012/public/schedule/detail/24261

 (There are some good slides attached to that web page)

 Take care,

 Lorin
 --
 Lorin Hochstein
 Lead Architect - Cloud Services
 Nimbis Services, Inc.
 www.nimbisservices.com




 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp




-- 
*Give me a place to stand, and I shall move the earth with a lever*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [HPC] Openstack HPC telecon

[Patrick Petit]

Hi John Paul  All,
11am EDT sounds perfectly fine with European TX. Regular Confcall format is
fine too.
Best regards,
Patrick
Le 6 juil. 2012 19:39, John Paul Walters jwalt...@isi.edu a écrit :

 Earlier is totally fine.  I want to strike a balance with the people on
 the west coast.  How about noon EDT or even 11am EDT?  Is that getting too
 early for the west coast?

 JP


 On Jul 6, 2012, at 11:55 AM, Tim Bell wrote:

 
  Would it be possible a bit earlier ? This would be 10pm in Europe so it
  would limit the participation.
 
  Tim
 
  -Original Message-
  From: openstack-bounces+tim.bell=cern...@lists.launchpad.net
  [mailto:openstack-bounces+tim.bell=cern...@lists.launchpad.net] On
 Behalf
  Of Narayan Desai
  Sent: 06 July 2012 17:08
  To: John Paul Walters
  Cc: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
  Subject: Re: [Openstack] [HPC] Openstack HPC telecon
 
  On Fri, Jul 6, 2012 at 9:51 AM, John Paul Walters jwalt...@isi.edu
  wrote:
 
  Does something like the first Monday of the month at 4:00pm EDT (UTC-4)
  work?  I'm just throwing out that time as something that seems to
 broadly
  work on my end, but I'd welcome any input from others.
 
  That generally works fine for me.
  -nld
 
  ___
  Mailing list: https://launchpad.net/~openstack
  Post to : openstack@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~openstack
  More help   : https://help.launchpad.net/ListHelp


 ___
 Mailing list: https://launchpad.net/~openstack
 Post to : openstack@lists.launchpad.net
 Unsubscribe : https://launchpad.net/~openstack
 More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Is openstack-glance package broken?

[Patrick Petit]

Hi there,

Trying to install OpenStack on Fedora 16 following instructions at
http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17

Very early in the installation process here is what I get. This is new to
me as previous installs worked okay at this point. Does it ring a bell ?
Thanks
Patrick

$ sudo openstack-db --service glance --init
Please enter the password for the 'root' MySQL user:
Verified connectivity to MySQL.
Creating 'glance' database.
Asking openstack-glance to sync the database.
Traceback (most recent call last):
  File /usr/bin/glance-manage, line 43, in module
from glance.common import cfg
ImportError: cannot import name cfg
ERROR 1146 (42S02) at line 1: Table 'glance.migrate_version' doesn't exist
Final sanity check failed.
Please file a bug report on bugzilla.redhat.com against the
openstack-glance package.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Re: [Openstack] [Nova] Getting error when injecting data into an image

[Patrick Petit]

2012/5/25 Pádraig Brady p...@draigbrady.com

 On 05/25/2012 09:10 AM, Patrick Petit wrote:
 
 
  2012/5/24 Pádraig Brady p...@draigbrady.com mailto:p...@draigbrady.com
 
  On 05/24/2012 02:49 PM, Patrick Petit wrote:
  
  
   2012/5/24 Pádraig Brady p...@draigbrady.com 
  mailto:p...@draigbrady.com
 mailto:p...@draigbrady.com mailto:p...@draigbrady.com
  
   On 05/24/2012 01:26 PM, Patrick Petit wrote:
Hi Pádraig,
   
Thank you for your reply.
   
I applied the suggested  libvirt_inject_partition = -1
   
It does change things because it's not complaining about
 mount error any more but generates further errors down the path in
 libvirt.py
  
2012-05-24 14:11:54 TRACE nova.compute.manager [instance:
 a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31]   File
 /usr/lib64/python2.7/site-packages/libvirt.py, line 540, in
 createWithFlags
2012-05-24 14:11:54 TRACE nova.compute.manager [instance:
 a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] if ret == -1: raise libvirtError
 ('virDomainCreateWithFlags() failed', dom=self)
2012-05-24 14:11:54 TRACE nova.compute.manager [instance:
 a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] libvirtError: internal error Process
 exited while reading console log output: char device redirected to
 /dev/pts/2
2012-05-24 14:11:54 TRACE nova.compute.manager [instance:
 a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] Could not allocate dynamic translator
 buffer
  
   That's libvirt specific.
  
   Do you have Virtual Machine support enabled in your BIOS?
   If not the fallback mode is currently disallowed by SELinux,
   and you can enable with: setsebool -P virt_use_execmem=on
  
   https://bugzilla.redhat.com/show_bug.cgi?id=753589#c36
  
   It's quite a non specific error so it could be something else.
  
   I am running the all OpenStack in a virtual machine under VBox.
   nova.conf has libvirt_type = qemu
  
   Disabling SELinux solved the problem.
   Shouldn't that be reported as a bug?
 
  I think the bug referenced above captures the issue sufficiently.
  What I've done is to document the specific SELinux setting above,
  to enable this mode of operation, in the fedora/epel wiki where
  you said you were following the instructions.
 
 
  Pádraig,
 
  Shouldn't the packages installation scripts take care of the SElinux
 configuration settings and make that transparent to end-users?
  After all, we might expect that once the various packages are installed
 on that distribution OpenStack just works out-of-the-box.

 As far as possible, yes.

 However I'd be wary about auto setting that parameter as the user
 could be using the VM for something else and so this security
 relaxation needs to be done explicitly at present.

 Also installing to a VM is not a production deployment scenario,
 so documenting the setting for testing/dev is OK for now I think.


Sure. sounds good to me.
Thank you for fixing the documentation.
Cheers,
Patrick


 We'll continue to monitor this issue and perhaps be able to work around it
 in future.

 cheers,
 Pádraig.




-- 
*Give me a place to stand, and I shall move the earth with a lever*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] [Nova] Getting error when injecting data into an image

[Patrick Petit]

Hi,
I am getting the following error when running

$ nova boot myserver --flavor 2 --key_name mykey --image
661bbe35-ebe5-4614-bdb2-3259ea507934

+-+--+

|   Property  |
Value |
+-+--+

| OS-DCF:diskConfig   |
MANUAL   |
| OS-EXT-SRV-ATTR:host|
None |
| OS-EXT-SRV-ATTR:hypervisor_hostname |
None |
| OS-EXT-SRV-ATTR:instance_name   |
instance-0005|
| OS-EXT-STS:power_state  |
0|
| OS-EXT-STS:task_state   |
scheduling   |
| OS-EXT-STS:vm_state |
building |
| accessIPv4
|  |
| accessIPv6
|  |
| adminPass   |
mAnfCStaqWT2 |
| config_drive
|  |
| created |
2012-05-23T13:49:12Z |
| flavor  |
m1.small |
| hostId
|  |
| id  |
18cde301-e8c9-4721-928b-cd0daf63a4f0 |
| image   |
f16-jeos |
| key_name|
mykey|
| metadata|
{}   |
| name|
myserver |
| progress|
0|
| status  |
BUILD|
| tenant_id   |
873855379940442797e53f2fa437893f |
| updated |
2012-05-23T13:49:13Z |
| user_id |
5677a018b8924cc58f993101c3024794 |
+-+--+



The image was obtained from following the Getting Started with OpenStack on
Fedora 17 tutorial (
http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_17).
So, I guess I am not the only one using it.

$ glance index

ID   Name   Disk
Format  Container Format Size

 --
  --

661bbe35-ebe5-4614-bdb2-3259ea507934 f16-jeos
qcow2ovf   213581824

c15e90f2-e73e-4987-ad7a-11d87403012e cirros-0.3.0-x86_64-ari
ari  ari 2254249

68ad4ece-6a56-4ac8-b112-1dd69283ea83 cirros-0.3.0-x86_64-ami
ami  ami25165824

6f5d8022-2dfe-406d-b391-fa0e48c175f3 cirros-0.3.0-x86_64-aki
aki  aki 4731440


This is running on Nova Essex on Fedora 16.
After a while I get:

$ nova list

+--+--++--+

|  ID  |   Name   | Status |
Networks |
+--+--++--+

| 18cde301-e8c9-4721-928b-cd0daf63a4f0 | myserver | ERROR  |
demonet=10.0.0.2 |
+--+--++--+



And so the log:

2012-05-23 15:50:12 INFO nova.virt.libvirt.connection [-] Compute_service
record updated for fedora.localdomain

2012-05-23 15:50:35 WARNING nova.virt.libvirt.connection
[req-dd9a661c-94d3-42e4-b7ba-699c7b41def4 5677a018b8924cc58f993101c3024794
873855379940442797e53f2fa437893f] [instance:
18cde301-e8c9-4721-928b-cd0daf63a4f0] Ignoring error injecting data into
image 661bbe35-ebe5-4614-bdb2-3259ea507934 (

-- 

Failed to mount filesystem: Unexpected error while running command.

Command: sudo nova-rootwrap mount /dev/mapper/nbd15p1 /tmp/tmpM9dOLC

Exit code: 32

Stdout: ''

Stderr: 'mount: you must specify the filesystem type\n'

-- 

Failed to mount filesystem: Unexpected error while running command.

Command: sudo nova-rootwrap guestmount --rw -a
/var/lib/nova/instances/instance-0005/disk -m /dev/sda1 /tmp/tmpM9dOLC

Exit code: 1

Stdout: ''

Stderr: libguestfs: error: mount_options: /dev/vda1 on /: mount: you must
specify the filesystem type\n/usr/bin/guestmount: '/dev/sda1' could not be
mounted.  Did you mean one of these?\n\t/dev/sda1 (unknown)\n\t/dev/sda2
(ext4)\n)


Note that I get the same error with other images, so it's not specific to
f16-jeos. I am confused by this error. If the nova-rootwrap had to specify
a filesystem type for the mount to succeed that would be a longtime known

Re: [Openstack] [Nova] Getting error when injecting data into an image

[Patrick Petit]

2012/5/24 Pádraig Brady p...@draigbrady.com

 On 05/24/2012 01:26 PM, Patrick Petit wrote:
  Hi Pádraig,
 
  Thank you for your reply.
 
  I applied the suggested  libvirt_inject_partition = -1
 
  It does change things because it's not complaining about mount error any
 more but generates further errors down the path in libvirt.py

  2012-05-24 14:11:54 TRACE nova.compute.manager [instance:
 a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31]   File
 /usr/lib64/python2.7/site-packages/libvirt.py, line 540, in
 createWithFlags
  2012-05-24 14:11:54 TRACE nova.compute.manager [instance:
 a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] if ret == -1: raise libvirtError
 ('virDomainCreateWithFlags() failed', dom=self)
  2012-05-24 14:11:54 TRACE nova.compute.manager [instance:
 a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] libvirtError: internal error Process
 exited while reading console log output: char device redirected to
 /dev/pts/2
  2012-05-24 14:11:54 TRACE nova.compute.manager [instance:
 a5d5b5c7-093a-4eb4-9d70-d6cfa2b30a31] Could not allocate dynamic translator
 buffer

 That's libvirt specific.

 Do you have Virtual Machine support enabled in your BIOS?
 If not the fallback mode is currently disallowed by SELinux,
 and you can enable with: setsebool -P virt_use_execmem=on

 https://bugzilla.redhat.com/show_bug.cgi?id=753589#c36

 It's quite a non specific error so it could be something else.

I am running the all OpenStack in a virtual machine under VBox.
nova.conf has libvirt_type = qemu

Disabling SELinux solved the problem.
Shouldn't that be reported as a bug?
Thanks a thousand times.
Patrick




 cheers,
 Pádraig.




-- 
*Give me a place to stand, and I shall move the earth with a lever*
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp