Hi All,
This is regarding Ironic service, I am having following queries on
Baremetal node, it would be great if anyone can help me to clarify it:
1. Baremetal Node is same as Compute Node and responsible for performing
necessary operations in order to provision BareMetal.
or
Baremetal Node is itself a provisioned BareMetal instance.
2. Is this possible to deploy baremetal using SAN storage?
Thanks & Regards
Ankit Agrawal
From: openstack-requ...@lists.openstack.org
To: openstack@lists.openstack.org
Date: 01/14/2015 05:41 PM
Subject: Openstack Digest, Vol 19, Issue 14
Send Openstack mailing list submissions to
openstack@lists.openstack.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
or, via email, send a message with subject or body 'help' to
openstack-requ...@lists.openstack.org
You can reach the person managing the list at
openstack-ow...@lists.openstack.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Openstack digest..."
Today's Topics:
1. How to reset neutron (to clear leftovers from incorrect
configuration) (Uwe Sauter)
2. Re: BUG: soft lockup messages (Giacomo Tenaglia)
3. Check host hardware (Bartek ?urawski)
4. Re: Check host hardware (gustavo panizzo (gfa))
5. Re: Check host hardware (Robert van Leeuwen)
6. Re: Openstack Ironic Installation in CentOS (Christopher Anderson)
7. Heat "Unknown property floating_network" Error (Richard Raseley)
8. Test (S?awek Kap?o?ski)
9. Re: Check host hardware (Belmiro Moreira)
10. Juno (Ubuntu) Flat Network (Ross Lillie)
11. Cinder api enpoint not found error while attach volume to
instance (Geo Varghese)
12. Re: [openstack-dev] Kilo devstack issue (Nikesh Kumar Mahalka)
----------------------------------------------------------------------
Message: 1
Date: Tue, 13 Jan 2015 15:00:01 +0100
From: Uwe Sauter <uwe.sauter...@gmail.com>
To: openstack@lists.openstack.org
Subject: [Openstack] How to reset neutron (to clear leftovers from
incorrect configuration)
Message-ID: <54b524e1.2080...@gmail.com>
Content-Type: text/plain; charset=utf-8
Hi all,
I'd like to get your comments on how to correctly clean a defective
neutron configuration so I can start over with a new config.
I'm currently running on CentOS 7 but try to keep it as generic as
possible (but the distro affects the service and package names?)
#### Compute hosts ####
1) stop service:
# systemctl stop neutron-openvswitch-agent.service
2) remove Openvswtch bridges:
# ovs-vsctl del-br br-tun
# ovs-vsctl del-br br-int
3) stop services:
# systemctl stop openvswitch.service
# systemctl stop openvswitch-nonetwork.service
4) remove Openvswitch persistent configuration
# rm -rf /etc/openvswitch/* /etc/openvswitch/.*
5) remove Openvswitch Kernel module
# rmmod openvswitch
6) optionally: reset configuration files:
# rm -rf /etc/neutron/*
# yum reinstall openstack-neutron openstack-neutron-ml2
openstack-neutron-openvswitch (or whatever plugins were installed
additionally)
#################################
#### Network host ####
1) stop services:
# systemctl stop neutron-l3-agent.service
# systemctl stop neutron-dhcp-agent.service
# systemctl stop neutron-metadata-agent.service
# systemctl stop neutron-openvswitch-agent.service
# systemctl stop neutron-ovs-cleanup.service
# systemctl stop neutron-openvswitch-agent.service
2) remove Openvswtch bridges:
# ovs-vsctl del-br br-tun
# ovs-vsctl del-br br-int
# ovs-vsctl del-br br-ex
3) stop services:
# systemctl stop openvswitch.service
# systemctl stop openvswitch-nonetwork.service
4) remove Openvswitch persistent configuration
# rm -rf /etc/openvswitch/* /etc/openvswitch/.*
5) remove Openvswitch Kernel module
# rmmod openvswitch
6) optionally: reset configuration files:
# rm -rf /etc/neutron/*
# yum reinstall openstack-neutron openstack-neutron-ml2
openstack-neutron-openvswitch (or whatever plugins were installed
additionally)
#################################
#### Neutron controller host ####
1) stop service:
# systemctl stop neutron-server.service
2) clear neutron database (on database host):
# mysql -u <DBADMIN> -p
mysql> drop database neutron;
mysql> create database neutron;
3) optionally: reset configuration files:
# rm -rf /etc/neutron/*
# yum reinstall openstack-neutron openstack-neutron-ml2 (or whatever
plugins were installed additionally)
#################################
When come to that point, one can begin configuring Neutron again from a
clean point. Don't forget to:
1) create a symlink on each host
/etc/neutron/plugin.ini -> /etc/neutron/plugins/ml2/ml2_conf.ini
2) sync the database on the controller host
3) configure Neutron
4) restart services on all hosts
Do I forget any step? Is there an easier way to get back the vanilla
state?
Best regards,
Uwe
------------------------------
Message: 2
Date: Tue, 13 Jan 2015 15:30:34 +0100
From: Giacomo Tenaglia <giacomo.tenag...@cern.ch>
To: <openstack@lists.openstack.org>
Subject: Re: [Openstack] BUG: soft lockup messages
Message-ID: <54b52c0a.6050...@cern.ch>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
On 09/01/15 13:01, Matej Mailing wrote:
> we have tweaked some NFS parameters for our backend storage, including
> packet sizes and now the load is constantly slower, there is much less
> I/O waiting. There were no lock-ups after that. So it really seems it
> was slow storage that was to be blamed. I will certainly report back
> if the failures occur again.
Hi Matej,
could you elaborate more on the tweaks you implemented on your NFS
servers, out of interest?
Thanks,
Giacomo
--
Giacomo Tenaglia
CERN IT Department
Systems Team - Database Group
http://phonebook.cern.ch/#id=PE671909
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5638 bytes
Desc: S/MIME Cryptographic Signature
URL: <
http://lists.openstack.org/pipermail/openstack/attachments/20150113/ffb9f9e1/attachment-0001.bin
>
------------------------------
Message: 3
Date: Tue, 13 Jan 2015 15:42:42 +0100
From: Bartek ?urawski <bartekzuraws...@gmail.com>
To: openstack@lists.openstack.org
Subject: [Openstack] Check host hardware
Message-ID:
<caa_np-hqr+8obunpdzb+pxhblrwzxlx2m8nwrx5qrkp5db6...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
Is it something like openstack way to check hardware of hosts (cpu, ram
etc.) before adding it to production environment ?
Thanks,
Bartek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.openstack.org/pipermail/openstack/attachments/20150113/04a9b6d8/attachment-0001.html
>
------------------------------
Message: 4
Date: Tue, 13 Jan 2015 13:06:24 -0300
From: "gustavo panizzo (gfa)" <g...@zumbi.com.ar>
To: Bartek ?urawski <bartekzuraws...@gmail.com>,
openstack@lists.openstack.org
Subject: Re: [Openstack] Check host hardware
Message-ID: <54b54280.9030...@zumbi.com.ar>
Content-Type: text/plain; charset=UTF-8
On 01/13/2015 11:42 AM, Bartek ?urawski wrote:
> Hi,
>
> Is it something like openstack way to check hardware of hosts (cpu, ram
> etc.) before adding it to production environment ?
no. afaik, i whish there were a capability to start a compute node as
disabled.
not start like a restart of the service or server. but the first time
nova-compute is started on a node it gets 'created' on the db i wish it
were created as disabled, so test can be run against it and if is ok,
enable it
what others are doing when add compute nodes?
--
1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
------------------------------
Message: 5
Date: Tue, 13 Jan 2015 17:11:43 +0000
From: Robert van Leeuwen <robert.vanleeu...@spilgames.com>
To: "gustavo panizzo (gfa)" <g...@zumbi.com.ar>, Bartek ?urawski
<bartekzuraws...@gmail.com>,
"openstack@lists.openstack.org"
<openstack@lists.openstack.org>
Subject: Re: [Openstack] Check host hardware
Message-ID:
<79e00d9220302d448c1d59b5224ed12d8ec62...@echodb02.spil.local>
Content-Type: text/plain; charset="iso-8859-2"
> no. afaik, i whish there were a capability to start a compute node as
> disabled.
+1
We do some magic in our flavors so instances go to specific hypervisors.
(we have hypervisors with a lot of fast local storage for io intensive
instances)
Happy side affect is that unless a hypervisor is in a specific host
aggregate it will not spawn machines.
However I would certainly want this to be an option.
Cheers,
Robert van Leeuwen
------------------------------
Message: 6
Date: Tue, 13 Jan 2015 11:57:47 -0700
From: Christopher Anderson <linuxgur...@gmail.com>
To: openstack@lists.openstack.org
Subject: Re: [Openstack] Openstack Ironic Installation in CentOS
Message-ID:
<capbbmkugb9jx78c2kay-5esphvzushp0zpoo0cs2z-6dxd+...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hello:
Im also had this issue
This worked for me you may have to add the fhel7 repo first but after that
this worked for me
yum install python-mock python-pyghmi
openstack-ironic-common-2014.2-2.el7.noarch.rpm
openstack-ironic-api-2014.2-2.el7.noarch.rpm
openstack-ironic-conductor-2014.2-2.el7.noarch.rpm
Let me know if that?s what your looking for after that it was straight
forward to follow the install for Ubuntu as a guide
Xopher Anderson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.openstack.org/pipermail/openstack/attachments/20150113/ccc506be/attachment-0001.html
>
------------------------------
Message: 7
Date: Tue, 13 Jan 2015 11:11:09 -0800
From: Richard Raseley <rich...@raseley.com>
To: openstack@lists.openstack.org
Subject: [Openstack] Heat "Unknown property floating_network" Error
Message-ID:
<CAO=6ox-hhac+va8x09gjkqbskogkdjf0rr+tqcffeenbjcl...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
This is RDO Icehouse-4 on CentOS 7
I am attempting to deploy a very basic stack using a slightly modified
version of a template found in openstack/heat-templates on GitHub[1].
However, both this base template and my modified vesion fail 'heat
template-validate'. Adding the debug flag revealed an inner exception
of 'heatclient.exc.
HTTPBadRequest: ERROR: Unknown Property
floating_network'.[2]
According to the documentation[3], 'floating_network' is a valid
property for 'OS::Neutron::FloatingIP'.
Can anyone provide some insight as to why this might be occurring?
[1] -
https://github.com/openstack/heat-templates/blob/master/hot/servers_in_new_neutron_net.yaml
[2] - https://gist.github.com/richardraseley/56373552e970f215928b
[3] -
http://docs.openstack.org/hot-reference/content/OS__Neutron__FloatingIP.html
------------------------------
Message: 8
Date: Tue, 13 Jan 2015 20:54:45 +0100
From: S?awek Kap?o?ski <sla...@kaplonski.pl>
To: openstack@lists.openstack.org
Subject: [Openstack] Test
Message-ID: <54b57805.5040...@kaplonski.pl>
Content-Type: text/plain; charset=utf-8; format=flowed
Hello,
This is only test
Slawek Kaplonski
sla...@kaplonski.pl
------------------------------
Message: 9
Date: Tue, 13 Jan 2015 21:00:32 +0100
From: Belmiro Moreira <moreira.belmiro.email.li...@gmail.com>
To: "gustavo panizzo (gfa)" <g...@zumbi.com.ar>
Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>
Subject: Re: [Openstack] Check host hardware
Message-ID:
<capkqhnc+s97yxnmgjvrdxijakcfsuzy3ljjmauwuyl8gdaa...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
you can use:
enable_new_services = False
With this option new services will be disabled when added.
There is also a proposed change to include a default disabled reason for
these services.
See: https://review.openstack.org/#/c/136645/
Belmiro
---
CERN
On Tuesday, January 13, 2015, gustavo panizzo (gfa) <g...@zumbi.com.ar>
wrote:
>
>
> On 01/13/2015 11:42 AM, Bartek ?urawski wrote:
> > Hi,
> >
> > Is it something like openstack way to check hardware of hosts (cpu,
ram
> > etc.) before adding it to production environment ?
>
> no. afaik, i whish there were a capability to start a compute node as
> disabled.
>
> not start like a restart of the service or server. but the first time
> nova-compute is started on a node it gets 'created' on the db i wish it
> were created as disabled, so test can be run against it and if is ok,
> enable it
>
> what others are doing when add compute nodes?
>
>
> --
> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
>
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org <javascript:;>
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.openstack.org/pipermail/openstack/attachments/20150113/3eff68aa/attachment-0001.html
>
------------------------------
Message: 10
Date: Wed, 14 Jan 2015 02:14:27 +0000
From: Ross Lillie <ross.lil...@motorolasolutions.com>
To: Openstack <openstack@lists.openstack.org>
Subject: [Openstack] Juno (Ubuntu) Flat Network
Message-ID:
<60751e11-81a3-4bd4-8654-8f62e5165...@motorolasolutions.com>
Content-Type: text/plain; charset="utf-8"
All,
I?ve just upgraded our cloud from Havana to Juno.
I?ve succeeded in configuring Neutron with a flat, external network and
individual tenants can attach to it via a virtual router and floating
address, using GRE tunnels. However, I also need to configure a simple
flat network for a given tenant that maps directly to our campus network
(i.e. WAN).
I?m having problems getting this configured correctly. Neutron is
configured entirely on its own node, with multiple interfaces: eth0 is
attached to our campus network and serves as the management interface,
br-ex (eth2) is attached to our campus backbone and is used to create the
?external" flat network, br-data (eth1) is attached to the cloud?s data
network. Compute nodes are configured with a single interface br-data
(eth0).
Now to create a simple flat network:
* can I share the br-ex interface or do I need to use a separate physical
interface on the network node? Neutron complains loudly when I try to do
this, so I suspect the answer is an emphatic NO.
* is a GRE tunnel still used for a simple flat network between the
compute nodes and the network node?
* when I bring up a separate external interface (call this br-ex2) and
try to create the simple flat network using this physical interface, then
when I try to boot an instance it fails with a ?No available host? found?,
with errors also in the nova-conductor log regarding vif interface mapping
problems.
I had this working in Havana using VLAN networks, but can?t seem to get
things working with GRE tunnels.
Any tips/pointers would be appreciated
?
Ross Lillie, Motorola Solutions
CTO, SST, Applications & Services Research
------------------------------
Message: 11
Date: Wed, 14 Jan 2015 12:55:07 +0530
From: Geo Varghese <gvargh...@aqorn.com>
To: "openstack@lists.openstack.org" <openstack@lists.openstack.org>,
"openstack-operat...@lists.openstack.org"
<openstack-operat...@lists.openstack.org>
Cc: "Britt Houser \(bhouser\)" <bhou...@cisco.com>
Subject: [Openstack] Cinder api enpoint not found error while attach
volume to instance
Message-ID:
<cadb-e-v51iazpttcnrrtjeggjjrefgykw__jzw7sq5jcxd2...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Team,
I need a help with cinder volume attachment with an instance.
I have succesfully created cinder volume and it is in available state.
Please check attached screenshot.
Later I tried to attach volume to an instance but attachment failed. While
checking logs in /var/log/nova/nova-api-os-compute.log
========
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack res =
method(self, ctx, volume_id, *args, **kwargs)
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack File
"/usr/lib/python2.7/dist-packages/nova/volume/cinder.py", line 206, in get
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack item =
cinderclient(context).volumes.get(volume_id)
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack File
"/usr/lib/python2.7/dist-packages/nova/volume/cinder.py", line 91, in
cinderclient
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack
endpoint_type=endpoint_type)
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack File
"/usr/lib/python2.7/dist-packages/cinderclient/service_catalog.py", line
80, in url_for
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack raise
cinderclient.exceptions.EndpointNotFound()
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack EndpointNotFound
2015-01-13 19:14:46.563 1736 TRACE nova.api.openstack
=========================================
I have already created endpints in v1 and v2.
Please check endpints I have created for cinder below
=========================================================================
root@controller:/home/geo# keystone endpoint-list | grep 8776
| 5c7bcc79daa74532ac9ca19949e0d872 | regionOne |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s |
http://controller:8776/v1/%(tenant_id)s | 8ce0898aa7c84fec9b011823d34b55cb
|
| 5d71e0a1237c483990b84c36346602b4 | RegionOne |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s |
http://controller:8776/v2/%(tenant_id)s | 251eca5fdb6b4550a9f521c10fa9f2ca
|
===============================================================================
Anyone please help me. Thanks for the support guys.
--
Regards,
Geo Varghese
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.openstack.org/pipermail/openstack/attachments/20150114/7e75cce2/attachment-0001.html
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot-Volumes & Snapshots - OpenStack Dashboard - Mozilla
Firefox.png
Type: image/png
Size: 97158 bytes
Desc: not available
URL: <
http://lists.openstack.org/pipermail/openstack/attachments/20150114/7e75cce2/attachment-0001.png
>
------------------------------
Message: 12
Date: Wed, 14 Jan 2015 15:06:24 +0530
From: Nikesh Kumar Mahalka <nikeshmaha...@vedams.com>
To: John Griffith <john.griffi...@gmail.com>
Cc: "openstack@lists.openstack.org" <openstack@lists.openstack.org>
Subject: Re: [Openstack] [openstack-dev] Kilo devstack issue
Message-ID:
<cakj7obzhc2i39g5p70wrtjqneyyxoa3+afv6tvxjz-seawr...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thanks its giving clear idea about console.
But what about ip not assigned to instance created in kilo devstack cloud.
Is any one facing the issue?
On Tue, Jan 13, 2015 at 12:51 AM, John Griffith <john.griffi...@gmail.com>
wrote:
> On Mon, Jan 12, 2015 at 10:03 AM, Nikesh Kumar Mahalka
> <nikeshmaha...@vedams.com> wrote:
> > Hi,
> > We deployed a kilo devstack on ubuntu 14.04 server.
> > We successfully launched a instance from dashboard, but we are unable
to
> > open console from dashboard for instance.Also instacne is unable to
get
> ip
> >
> > Below is link for local.conf
> > http://paste.openstack.org/show/156497/
> >
> >
> >
> > Regards
> > Nikesh
> >
> >
>
__________________________________________________________________________
> > 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
> >
> Correct, see this thread:
>
http://lists.openstack.org/pipermail/openstack-dev/2015-January/054157.html
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.openstack.org/pipermail/openstack/attachments/20150114/a0ad6009/attachment-0001.html
>
------------------------------
_______________________________________________
Openstack mailing list
openstack@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
End of Openstack Digest, Vol 19, Issue 14
*****************************************
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
