Fwd: Re: Quickstart and containers
by Boris
Forwarding message of James LaBarre to mailing lists
Boris.
-------- Пересылаемое сообщение --------
От кого: James LaBarre <jlabarre(a)redhat.com>
Кому: users(a)lists.rdoproject.org
Дата: Пятница, 16 февраля 2018, 2:02 +03:00
Тема: Re: [rdo-users] Quickstart and containers
(meant to send this to the general
list)
On 02/09/2018 01:03 PM, Boris wrote:
>
>
>
>>Пятница, 9 февраля 2018, 19:17 +03:00 от
>> James LaBarre <jlabarre(a)redhat.com> :
>>
>>If I am trying
>> to familiarize myself with the newer containerized
>>overcloud (Queens & upwards), is there a way to
>> build a TripleO
>>Quickstart on a single node?
> Due to I cannot any longer respond from hotmail.com ( backup
> address is used )
>
> 1. https://www.anstack.com/blog/2018/01/05/tripleo-quickstart-cheatsheet.html
> 2. this one was done via F27 connection to VIRTHOST
> http://lxer.com/module/newswire/view/252059/index.html
>
> I believe it might work in the way suggested by Carlos Camacho
> (1)
>
> Boris.
I tried the script as suggest by Carlos Camacho that you linked
above. As user "stack" it would fail when it was running the
teardown process, and would kill the user task before it finished.
So as a test I ran it as root, and it went through the
provision/teardown steps, but in the process wiped out everything
in the /home/stack directory (and I think removed the user since I
can no longer log into it.
Using a combination of both instructions, I cloned the git repos
locally for tripleo-quickstart tripleo-quickstart-extras
tripleo-environments tripleo-heat-templates tripleo-ui (needed the
heat templates for Carlos' directions). I'll have to poke through
the templates & see if I can figure out more.
Used the commands:
===================================
export CONFIG=/home/stack/deploy-configHA.yaml
export VIRTHOST=127.0.0.2
export OOOtimestamp=`date +%Y%m%d_%H%M`
bash ./tripleo-quickstart/quickstart.sh --clean --release queens
--teardown all --tags all -e @$CONFIG $VIRTHOST |& tee
~/OOOlog_${OOOtimestamp}.txt
_______________________________________________
users mailing list
users(a)lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users
To unsubscribe: users-unsubscribe(a)lists.rdoproject.org
----------------------------------------------------------------------
С уважением,
Boris Derzhavets
dba477(a)list.ru
6 years, 2 months
Fwd: Re: Quickstart and containers
by Boris
Forwarding message of James LaBarre to mailing lists
Boris.
-------- Пересылаемое сообщение --------
От кого: James LaBarre <jlabarre(a)redhat.com>
Кому: Boris <dba477(a)list.ru>
Дата: Пятница, 16 февраля 2018, 2:02 +03:00
Тема: Re: [rdo-users] Quickstart and containers
On 02/15/2018 05:17 PM, Boris wrote:
> Problems started right after I responded you the very first time from
> Runet Everything worked fine until 02/11/18
> See all three the most recent posts here
> http://lxer.com/module/newswire/byuser.php?user=dba477
>
Sorry, meant to reply to the general list, didn't check my outgoing address.
----------------------------------------------------------------------
Thanks
Boris Derzhavets
dba477(a)list.ru
6 years, 2 months
[Meeting] RDO meeting (2018-02-14) minutes
by Haïkel
==============================
#rdo: RDO meeting - 2018-02-14
==============================
Meeting started by number80 at 15:00:16 UTC. The full logs are
available at
http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_02_14/2018/rdo...
.
Meeting summary
---------------
* roll call (number80, 15:00:23)
* virtual meetup, April, 12th CFP (number80, 15:03:00)
* LINK: https://goo.gl/e5EWAt (rbowen, 15:03:53)
* if you want to present a project, feature, Return on Experience
about OpenStack, please submit to CfP (number80, 15:04:15)
* LINK: https://etherpad.openstack.org/p/rdo-queens-release (rbowen,
15:07:17)
* Queens Release checklist (number80, 15:08:11)
* help required to write RDO Queens release notes! (number80,
15:08:34)
* ACTION: jpena to extract contributor list and numbers from
repoxplorer (jpena, 15:11:25)
* Test day preparedness (number80, 15:11:57)
* ACTION: rbowen will update testday web site, send announce to lists
(rbowen, 15:15:07)
* AGREED: move test day to March 15, 16 as final release test days
(number80, 15:15:14)
* Follow-up: CentOS Cloud SIG meetings? (number80, 15:18:05)
* ACTION: look at the poll result and send results on centos-devel
list (number80, 15:18:43)
* LINK: http://whenisgood.net/bpqn4fn (rbowen, 15:19:32)
* Follow-up: stabilized repositories proposal (number80, 15:22:17)
* LINK:
https://etherpad.openstack.org/p/stabilized-fedora-repositories-for-opens...
(number80, 15:22:43)
* next week chair (number80, 15:27:27)
* jpena chairing next week meeting (number80, 15:28:39)
* open floor (and celebration for leanderthal come back) (number80,
15:28:56)
* leanderthal is back :) (number80, 15:29:02)
Meeting ended at 15:32:50 UTC.
Action items, by person
-----------------------
* jpena
* jpena to extract contributor list and numbers from repoxplorer
* rbowen
* rbowen will update testday web site, send announce to lists
People present (lines said)
---------------------------
* number80 (68)
* rbowen (50)
* dmsimard (12)
* openstack (10)
* leanderthal (8)
* amoralej (8)
* jpena (5)
* rdogerrit (3)
* ykarel (3)
* dtantsur (2)
* jruzicka (2)
* weshay (1)
* apevec (1)
* jschlueter (1)
* mjturek (1)
* mary_grace (1)
Generated by `MeetBot`_ 0.1.4
6 years, 2 months
Python3 proposal: stabilized Fedora repositories for OpenStack
by Haïkel
Hi,
Following our discussions during today's RDO meeting about a draft to
start working on
python3 support in RDO, I expand the discussion to the wider group.
Please keep the discussion on the dev list, users list is only there
to raise awareness.
Since it's a huge topic, I started an etherpad to collect our
thoughts. It is on upstream etherpad
in order to collaborate with upstream as we hope this would be useful
for upstream gating.
Please read the etherpad for details and provide your feedback.
https://etherpad.openstack.org/p/stabilized-fedora-repositories-for-opens...
The main idea is to use stabilized Fedora repositories, it is a lot of
work and we intend to start
working that during the Rocky cycle. This will allow us to work on
migrating our packaging on python3
and support modularity which will ship with EL8 (currently a Fedora
only feature).
There's a lot of work but we aim to be ready on time to migrate to
Python3 when EL8 will be released.
This is not about supporting python3 for end-users, until EL8 gets
released, this is only intended
for our downstream and upstream CI pipelines.
Regards,
H.
6 years, 2 months
Announcing mail.rdoproject.org service
by Rich Bowen
I wanted to let you all know about the mail.rdoproject.org service. It's
been there a while, but we've just put the hostname in place and
prettied it up for you.
mail.rdoproject.org is running on the Apache PonyMail software
(http://ponymail.apache.org/) and provides a web-based interface to our
mailing lists. This lets you, among other things:
* Revive an old thread from before you were subscribed
* See basic statistics about participation in mailing list threads
* Advanced searching features
* oAuth authentication - if there's an auth source you want to use
that's not there, let us know, and we'll add it
* Compose email in the web interface or in your own mail client, as you
prefer
* Keyboard shortcuts! (Press H for a list)
PonyMail is, of course, open source (Apache license), if you want to
help make it better.
--
Rich Bowen - rbowen(a)redhat.com
@RDOcommunity // @CentOSProject // @rbowen
6 years, 2 months
RHOSP 10 failed registration of the overcloud nodes
by Anda Nicolae
Hello,
I am trying to deploy OpenStack 10 using OpenStack Platform Director 10.
I am using a bare-metal server with RedHat 7.4, on which I have created 3 VMs: 1st VM is the undercloud node, 2nd VM is the overcloud controller node and the 3rd VM is the overcloud compute node.
The bare-metal server I am using is also my KVM hypervisor for the overcloud.
The bare-metal server has 2 interfaces: an external interface used in instackenv.json for registering the overcloud nodes and a provisioning interface which will be used for provisioning the overcloud nodes.
My 1st question is: Is it mandatory that the KVM hypervisor for the overcloud VMs and the undercloud are the same machine?
As you can see, in my case the undercloud VM and the KVM hypervisor are different machines.
I saw a blog post which used a topology similar to mine: https://keithtenzer.com/2017/04/20/red-hat-openstack-platform-10-newton-i...
The error I am getting while running:
openstack baremetal import -- json ~/.instackenv.json
is in ironic_conductor.log: Failed to validate power driver interface for node <uuid>. Error: SSH connection cannot be established: Failed to establish SSH connection to host <kvm_hypervisor_external_ip_address >
I have created the instackenv.json file which looks similar to this:
"arch": "x86_64",
"host-ip": "<kvm_hypervisor_external_ip_address>",
"power_manager": "nova.virt.baremetal.virtual_power_driver.VirtualPowerManager",
"ssh-user": "stack",
"ssh-key": "$(cat ~/.ssh/id_rsa)",
"nodes": [
{
"mac": [
"<overcloud_controller_provisioning_interface_mac_address>"
],
"name": "overcloud-controller",
"capabilities" : "profile:control",
"cpu": "4",
"memory": "6000",
"disk": "50",
"arch": "x86_64",
"pm_user": "stack",
"pm_addr": "<kvm_hypervisor_external_ip_address>",
"pm_password": "$(cat ~/.ssh/id_rsa)",
"pm_type": "pxe_ssh"
}
,
{
"mac": [
"<overcloud_compute_provisioning_interface_mac_address>"
],
"name": "overcloud-compute",
"capabilities" : "profile:compute",
"cpu": "4",
"memory": "6000",
"disk": "50",
"arch": "x86_64",
"pm_user": "stack",
"pm_addr": "<kvm_hypervisor_external_ip_address>",
"pm_password": "$(cat ~/.ssh/id_rsa)",
"pm_type": "pxe_ssh"
}
]
}
Do you have any idea what might have gone wrong and how can I progress with my overcloud node registration?
Thanks,
Anda
6 years, 2 months
[Meeting] RDO meeting (2018-02-08) minutes
by Alfredo Moralejo Alonso
==============================
#rdo: RDO meeting - 2018-02-07
==============================
Meeting started by amoralej at 15:01:19 UTC. The full logs are
available athttp://eavesdrop.openstack.org/meetings/rdo_meeting___2018_02_07/2018/r...
.
Meeting summary
---------------
* roll call (amoralej, 15:01:29)
* ppc64le status (amoralej, 15:05:20)
* Missing packages:
https://lists.rdoproject.org/pipermail/dev/2018-February/008537.html
(should be fixed now) (amoralej, 15:05:44)
* python3 proposal: stabilized fedora for OpenStack (amoralej,
15:09:31)
* ACTION: number80 publish draft on the list and kickstart the
discussion on the list (number80, 15:22:42)
* RDO test days delayed - Feb 15, 16.
http://rdoproject.org/testday/queens/milestone3/ (amoralej, 15:30:23)
* Rohit Yadav - Guest from CloudStack to talk about their participation
in the Cloud SIG (amoralej, 15:34:04)
* LINK: http://cloudstack.apache.org (rohityadav, 15:35:43)
* LINK: http://packages.shapeblue.com/cloudstack/upstream/
(rohityadav, 15:35:53)
* LINK:
https://wiki.centos.org/SIGGuide#head-2e2e639e9d3d1feb0c7aba15213a909fccb...
(number80, 15:38:43)
* Virtual meetup possible dates: [ April 12th, 19th ] Times:?
(amoralej, 15:45:33)
* ACTION: rbowen to send a mail to RDO ML about virtual meetup planing
and asking for talk submissions (amoralej, 15:51:05)
* chair for next meeting (amoralej, 15:51:18)
* ACTION: number80 to chair next meeting (amoralej, 15:52:26)
* open floor (amoralej, 15:52:51)
Meeting ended at 16:01:27 UTC.
Action items, by person
-----------------------
* number80
* number80 publish draft on the list and kickstart the discussion on
the list
* number80 to chair next meeting
* rbowen
* rbowen to send a mail to RDO ML about virtual meetup planing and
asking for talk submissions
People present (lines said)
---------------------------
* amoralej (65)
* number80 (64)
* dmsimard (35)
* rbowen (33)
* rohityadav (19)
* dahn (9)
* jpena (8)
* openstack (6)
* chandankumar (5)
* mjturek (5)
* ykarel (4)
* jruzicka (4)
* mary_grace (2)
* baha (1)
Generated by `MeetBot`_ 0.1.4
Sorry for the delay
6 years, 3 months
Fwd: [openstack-dev] Feb 8 CFP Deadline - OpenStack Summit Vancouver
by Rich Bowen
FYI, in case you missed this, the call for papers for the Vancouver
OpenStack Summit closes TOMORROW.
Note, also, that 'RDO' is now on official tag that you can associate
with your talk submission, so let's give them a bunch of talks to
justify that decision.
-------- Forwarded Message --------
Subject: [openstack-dev] Feb 8 CFP Deadline - OpenStack Summit Vancouver
Date: Tue, 6 Feb 2018 14:18:23 -0600
From: Kendall Waters <kendall(a)openstack.org>
Reply-To: OpenStack Development Mailing List (not for usage questions)
<openstack-dev(a)lists.openstack.org>
To: openstack-dev(a)lists.openstack.org,
OpenStack-operators(a)lists.openstack.org,
women-of-openstack(a)lists.openstack.org, Community(a)lists.openstack.org,
marketing(a)lists.openstack.org
Hi everyone,
The Vancouver Summit
<https://www.openstack.org/summit/vancouver-2018/> CFP closes in two
days: February 8 at 11:59pm Pacific Time (February 9 at 6:59am UTC).
For the Vancouver, the Summit Tracks have evolved to cover the entire
open infrastructure landscape. Get your talks in for:
• Container infrastructure
• Edge computing
• CI/CD
• HPC/GPU/AI
• Open source community
• OpenStack private, public and hybrid cloud
The Programming Committees for each Track have provided suggest topics
for Summit sessions. View topic ideas for each track
<https://www.openstack.org/summit/vancouver-2018/summit-categories/> and
submit your proposals
<https://www.openstack.org/summit/vancouver-2018/call-for-presentations/> before
this week's deadline!
If you have any questions, please email summit(a)openstack.org
<mailto:summit@openstack.org>.
Cheers,
Kendall
Kendall Waters
OpenStack Marketing
kendall(a)openstack.org <mailto:kendall@openstack.org>
6 years, 3 months
