date:20141106

Re: [openstack-dev] OVF/OVA support

2014-11-06 Thread Davanum Srinivas

Malini,

fyi, Vui/Arnaud is leading the charge in the Nova VMware driver with
this review [1]. There is a spec in Nova also for multiple disks (for
a single vm) from Tesshu [2].

thanks,
dims

[1] https://review.openstack.org/#/c/82715/
[2] https://review.openstack.org/#/c/128691/

On Thu, Nov 6, 2014 at 3:06 AM, Bhandaru, Malini K
malini.k.bhand...@intel.com wrote:
 Please join us on Friday in the Glance track – free format session, to
 discuss supporting OVF/OVA in OpenStack.



 Poll:

 1)  How interested are you in this feature? 0 – 10

 2)  Interested enough to help develop the feature?





 Artifacts are ready for use.



 We are considering defining an artifact for OVF/OVA.

 What should the scope of this work be? Who are our fellow travelers?

 Intel is interested in parsing OVF meta data associated with images – to
 ensure that a VM image lands on the most appropriate hardware in the cloud
 instance, to ensure optimal performance.

 The goal is to remove the need to manually specify image meta data, allow
 the appliance provider to specify HW requirements, and in so doing reduce
 human error.

 Are any partners interested in writing an OVF/OVA artifact = stack
 deployment? Along the lines of heat?

 As a first pass, Intel we could at least

 1)  Defining artifact for OVA, parsing the OVF in it, pulling out the
 images therein and storing them in the glance image database and attaching
 meta data to the same.

 2)  Do not want to imply that OpenStack supports OVA/OVF -- need to be
 clear on this.

 3)  An OpenStack user could create a heat template using the images
 registered in step -1

 4)  OVA to Heat – there may be a loss in translation! Should we attempt
 this?

 5)  What should we do with multiple volume artifacts?

 6)  Are volumes read-only? Or on cloning, make copies of them?


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




-- 
Davanum Srinivas :: https://twitter.com/dims

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

[openstack-dev] [Nova][Schedule] how to schedule vms(like database VM, vs web server VM) to different resource pool(either LVM or GlusterFs)?

2014-11-06 Thread zhang xiaobin

Greeting,

I have some hosts in one availability zone, some hosts are solely based on LVM, 
which means their root images will be sitting on LVM;
while other hosts are setup with GlusterFS, which means their root image will 
be allocated on Gluster.

My question is: what's the best way to let VM be scheduled to the right 
resource pool(either LVM-based, or GlusterFs-based?)
how to configure and which kind of schedule filter to be used? can we use image 
metadata function to achieve this?

Many thanks!
本邮件（包括其附件）可能含有保密、专有或保留著作权的信息。如果您并非本邮件指定接受人，请即刻通知发送人并将本邮件从您的系统中删除，您不得散布、保留、复制、披露或以其他方式使用本邮件任何相关信息，并且通过邮件告知我们此次错误投递。发送人在本邮件下表达的观点并不一定代表苏宁云商集团股份有限公司的观点。苏宁云商集团股份有限公司并不保证本邮件是安全或不受任何计算机病毒影响的，并且对由于邮件传输而导致的邮件内容错误或缺失不承担任何责任。除非明确说明，本邮件并不构成具有约束力的契约。

This e-mail may contain confidential, copyright and/or privileged information. 
If you are not the addressee or authorized to receive this, please inform us of 
the erroneous delivery by return e-mail, and you should delete it from your 
system and may not use, copy, disclose or take any action based on this e-mail 
or any information herein. Any opinions expressed by sender hereof do not 
necessarily represent those of SUNING COMMERCE GROUP CO., LTD.,SUNING COMMERCE 
GROUP CO., LTD.,does not guarantee that this email is secure or free from 
viruses. No liability is accepted for any errors or omissions in the contents 
of this email, which arise as a result of email transmission. Unless expressly 
stated,this email is not intended to form a binding contract.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] pci pass through turing complete config options?

2014-11-06 Thread Doug Hellmann


On Nov 4, 2014, at 2:07 PM, Robert Li (baoli) ba...@cisco.com wrote:

 
 
 On 11/3/14, 6:32 PM, Doug Hellmann d...@doughellmann.com wrote:
 
 
 On Oct 31, 2014, at 9:27 PM, Robert Li (baoli) ba...@cisco.com wrote:
 
 
 
 On 10/28/14, 11:01 AM, Daniel P. Berrange berra...@redhat.com wrote:
 
 On Tue, Oct 28, 2014 at 10:18:37AM -0400, Jay Pipes wrote:
 On 10/28/2014 07:44 AM, Daniel P. Berrange wrote:
 One option would be a more  CSV like syntax eg
 
  pci_passthrough_whitelist =
 address=*0a:00.*,physical_network=physnet1
  pci_passthrough_whitelist = vendor_id=1137,product_id=0071
 
 But this gets confusing if we want to specifying multiple sets of
 data
 so might need to use semi-colons as first separator, and comma for
 list
 element separators
 
  pci_passthrough_whitelist = vendor_id=8085;product_id=4fc2,
 vendor_id=1137;product_id=0071
 
 What about this instead (with each being a MultiStrOpt, but no comma
 or
 semicolon delimiters needed…)?
 
 This is easy for a developer to access, but not easy for a deployer to
 make sure they have configured correctly because they have to keep up
 with the order of the options instead of making sure there is a new group
 header for each set of options.
 
 
 [pci_passthrough_whitelist]
 # Any Intel PRO/1000 F Sever Adapter
 vendor_id=8086
 product_id=1001
 address=*
 physical_network=*
 # Cisco VIC SR-IOV VF only on specified address and physical network
 vendor_id=1137
 product_id=0071
 address=*:0a:00.*
 physical_network=physnet1
 
 I think this is reasonable, though do we actually support setting
 the same key twice ?
 
 Yes, if it is registered in different groups.
 
 
 As an alternative we could just append an index for each element
 in the list, eg like this:
 
 [pci_passthrough_whitelist]
 rule_count=2
 
 # Any Intel PRO/1000 F Sever Adapter
 vendor_id.0=8086
 
 Be careful about constructing the names. You can’t have “.” in them
 because then you can’t access them in python, for example:
 cfg.CONF.pci_passthrough_whitelist.vendor_id.0
 
 product_id.0=1001
 address.0=*
 physical_network.0=*
 
 # Cisco VIC SR-IOV VF only on specified address and physical network
 vendor_id.1=1137
 product_id.1=0071
 address.1=*:0a:00.*
 physical_network.1=physnet1
 [pci_passthrough_whitelist]
 rule_count=2
 
 # Any Intel PRO/1000 F Sever Adapter
 vendor_id.0=8086
 product_id.0=1001
 address.0=*
 physical_network.0=*
 
 # Cisco VIC SR-IOV VF only on specified address and physical network
 vendor_id.1=1137
 product_id.1=0071
 address.1=*:0a:00.*
 physical_network.1=physnet1
 
 Or like this:
 
 [pci_passthrough]
 whitelist_count=2
 
 [pci_passthrough_rule.0]
 # Any Intel PRO/1000 F Sever Adapter
 vendor_id=8086
 product_id=1001
 address=*
 physical_network=*
 
 [pci_passthrough_rule.1]
 # Cisco VIC SR-IOV VF only on specified address and physical network
 vendor_id=1137
 product_id=0071
 address=*:0a:00.*
 physical_network=physnet1
 
 Yeah, The last format (copied in below) is a good idea (without the
 section for the count) to handle list of dictionaries. I¹ve seen similar
 config examples in neutron code.
 [pci_passthrough_rule.0]
 # Any Intel PRO/1000 F Sever Adapter
 vendor_id=8086
 product_id=1001
 address=*
 physical_network=*
 
 [pci_passthrough_rule.1]
 # Cisco VIC SR-IOV VF only on specified address and physical network
 vendor_id=1137
 product_id=0071
 address=*:0a:00.*
 physical_network=physnet1
 
 Without direct oslo support, to implement it requires a small method
 that
 uses oslo cfg¹s MultiConfigParser().
 
 I’m not sure what you mean needs new support? I think this would work,
 except for the “.” in the group name.
 
 The group header is not fixed in this case. Let’s replace “.” with “:”,
 then the user may have configured multiple groups such as
 [pci_passthrough_rule:x]. With oslo, how would you register the group and
 the options under it and access them as a list of dictionaries?

First, you MUST pick a separator character that results in the group name being 
a valid python variable name. So, instead of “:” use “_”. That gives you 
“pci_passthrough_rule_x”. Then you just pass that name when you register the 
list of options. See the second example under 
http://docs.openstack.org/developer/oslo.config/cfg.html#option-groups

Knowing which groups must exist is a separate problem, and solving that depends 
on the application. A common solution is to have a single option win a 
well-known group with a list of the names. For example, “pci_passthrough_rules 
= x, y, z” can be converted into the longer group names to register the option 
groups and then access their values.

 
 
 
 Now a few questions if we want to do it in Kilo:
 ‹ Do we still need to be back-ward compatible in configuring the
 whitelist? If we do, then we still need to be able to handle the json
 docstring.
 
 If there is code released using that format, you need to support it. You
 can define options as being deprecated so the new options replace the old
 but the old are available if found in

Re: [openstack-dev] [nova] pci pass through turing complete config options?

2014-11-06 Thread Doug Hellmann


On Nov 4, 2014, at 2:38 PM, melanie witt melwi...@gmail.com wrote:

 On Nov 4, 2014, at 0:32, Doug Hellmann d...@doughellmann.com wrote:
 
 I think this is reasonable, though do we actually support setting
 the same key twice ?
 
 Yes, if it is registered in different groups.
 
 I have found that for a MultiStrOpt, the same key can be set multiple times 
 even in the same group, and the result is a list of values for that option 
 [0].

Yes, that’s the purpose of MultiStrOpt. However, it is meant to hold a list of 
related items, not a list of instances of values that are essentially 
attributes of unrelated objects. If you have more than one property for a PCI 
passthrough device, you will need a separate MultiStrOpt for each one. The user 
will then have to ensure that they specify their options and values in order 
within their configuration file so that the separate arrays are populated 
consistently so the values in position 0 are all related and the values in 
position 1 are all related, etc. That is much more error prone then defining 
new groups and taking advantage of the syntax of the configuration file to help 
the user understand that a block of options is all related.

Now, all of that said, I still think you should just use a YAML file for this 
data.

Doug

 
 [0] 
 https://github.com/openstack/oslo.config/blob/11ecf18/oslo/config/cfg.py#L1011
 ___
 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

Re: [openstack-dev] [Nova][Schedule] how to schedule vms(like database VM, vs web server VM) to different resource pool(either LVM or GlusterFs)?

2014-11-06 Thread Chen CH Ji

I think you can refer to following for more info
http://blog.csdn.net/tantexian/article/details/39055889
http://blog.russellbryant.net/2013/05/21/availability-zones-and-host-aggregates-in-openstack-compute-nova/

And this is mail list for developers ,so you can ask openstack mail list if
you have configuration or questions next time :)

Best Regards!

Kevin (Chen) Ji 纪 晨

Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN   Internet: jiche...@cn.ibm.com
Phone: +86-10-82454158
Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC



From:   zhang xiaobin 14050...@cnsuning.com
To: openstack-dev openstack-dev@lists.openstack.org
Date:   11/06/2014 04:23 PM
Subject:[openstack-dev] [Nova][Schedule] how to schedule vms(like
databaseVM, vs web server VM) to different resource pool
(either LVM or  GlusterFs)?



 Greeting,

 I have some hosts in one availability zone, some hosts are solely based on
 LVM, which means their root images will be sitting on LVM;
 while other hosts are setup with GlusterFS, which means their root image
 will be allocated on Gluster.

 My question is: what's the best way to let VM be scheduled to the right
 resource pool(either LVM-based, or GlusterFs-based?)
 how to configure and which kind of schedule filter to be used? can we use
 image metadata function to achieve this?

 Many thanks!
 本邮件（包括其附件）可能含有保密、专有或保留著作权的信息。如果您并非本邮件
 指定接受人，请即刻通知发送人并将本邮件从您的系统中删除，您不得散布、保
 留、复制、披露或以其他方式使用本邮件任何相关信息，并且通过邮件告知我们此次
 错误投递。发送人在本邮件下表达的观点并不一定代表苏宁云商集团股份有限公司的
 观点。苏宁云商集团股份有限公司并不保证本邮件是安全或不受任何计算机病毒影响
 的，并且对由于邮件传输而导致的邮件内容错误或缺失不承担任何责任。除非明确说
 明，本邮件并不构成具有约束力的契约。
 This e-mail may contain confidential, copyright and/or privileged
 information. If you are not the addressee or authorized to receive this,
 please inform us of the erroneous delivery by return e-mail, and you
 should delete it from your system and may not use, copy, disclose or take
 any action based on this e-mail or any information herein. Any opinions
 expressed by sender hereof do not necessarily represent those of SUNING
 COMMERCE GROUP CO., LTD.,SUNING COMMERCE GROUP CO., LTD.,does not
 guarantee that this email is secure or free from viruses. No liability is
 accepted for any errors or omissions in the contents of this email, which
 arise as a result of email transmission. Unless expressly stated,this
 email is not intended to form a binding contract.
 ___
 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

Re: [openstack-dev] [Fuel] fuel master monitoring

2014-11-06 Thread Anton Zemlyanov

We can add a notification to FuelWeb, no additional software or user
actions are required. I would not overestimate this method though, it is in
no way the robust monitoring system. Forcing user to do something on a
regular basis is unlikely to work.

Anton

On Thu, Nov 6, 2014 at 11:55 AM, Przemyslaw Kaminski pkamin...@mirantis.com
wrote:

I think we're missing the point here. What I meant adding a simple
monitoring system that informed the user via UI/CLI/email/whatever of low
resources on fuel master node. That's it. HA here is not an option -- if,
despite of warnings, the user still continues to use fuel and disk becomes
full, it's the user's fault. By adding these warnings we have a way of
saying We told you so! Without warnings we get bugs like [1] I mentioned
in the first post.

Of course user can check disk space by hand but since we do have a
full-blown UI telling the user to periodically log in to the console and
check disks by hand seems a bit of a burden.

We can even implement such monitoring functionality as a Nailgun plugin --
installing it would be optional and at the same time we would grow our
plugin ecosystem.

On 11/05/2014 08:42 PM, Dmitry Borodaenko wrote:

Even one additional hardware node required to host the Fuel master is seen
by many users as excessive. Unless you can come up with an architecture
that adds HA capability to Fuel without increasing its hardware footprint
by 2 more nodes, it's just not worth it.

The only operational aspect of the Fuel master node that you don't want to
lose even for a short while is logging. You'd be better off redirecting
OpenStack environments' logs to a dedicated highly available logging server
(which, of course, you already have in your environment), and deal with
Fuel master node failures by restoring it from backups.

On Wed, Nov 5, 2014 at 8:26 AM, Anton Zemlyanov azemlya...@mirantis.com
wrote:

Monitoring of the Fuel master's disk space is the special case. I
really wonder why Fuel master have no HA option, disk overflow can be
predicted but many other failures cannot. HA is a solution of the 'single
point of failure' problem.

The current monitoring recommendations (
http://docs.openstack.org/openstack-ops/content/logging_monitoring.html)
are based on analyzing logs and manual checks, that are rather reactive way
of fixing problems. Zabbix is quite good for preventing failures that are
predictable but for the abrupt problems Zabbix just reports them 'post
mortem'.

The only way to remove the single failure point is to implement
redundancy/HA

Anton

On Tue, Nov 4, 2014 at 6:26 PM, Przemyslaw Kaminski
pkamin...@mirantis.com wrote:

Hello,

In extension to my comment in this bug [1] I'd like to discuss the
possibility of adding Fuel master node monitoring. As I wrote in the
comment, when disk is full it might be already too late to perform any
action since for example Nailgun could be down because DB shut itself down.
So we should somehow warn the user that disk is running low (in the UI and
fuel CLI on stderr for example) before it actually happens.

For now the only meaningful value to monitor would be disk usage -- do
you have other suggestions? If not then probably a simple API endpoint with
statvfs calls would suffice. If you see other usages of this then maybe it
would be better to have some daemon collecting the stats we want.

If we opted for a daemon, then I'm aware that the user can optionally
install Zabbix server although looking at blueprints in [2] I don't see
anything about monitoring Fuel master itself -- is it possible to do?
Though the installation of Zabbix though is not mandatory so it still
doesn't completely solve the problem.

88 matches

Mail list logo