Thanks, Boris.
I was able to get the instance running, but in Step 7, when I used the
command
# ssh -i cloud2.pem fedora(a)172.24.4.227
It returned
"ssh: connect to host 172.24.4.227 port 22: Connection timed out"
In the Dashboard is says that the instance is "active" and power state is
"running".
On Wed, Feb 17, 2016 at 2:04 PM, Boris Derzhavets <bderzhavets(a)hotmail.com>
wrote:
------------------------------
*From:* John Alway <jalway(a)gmail.com>
*Sent:* Wednesday, February 17, 2016 1:42 PM
*To:* Boris Derzhavets
*Cc:* rdo-list(a)redhat.com
*Subject:* Re: [Rdo-list] The RDO Quickstart Guide and Private Network
Thanks a lot for the help, Boris. I'll try this out. However, a lot
of these concepts I'm not sure of, so I'll have to study them.
Is this RDO project for beginners, or do they expect you to have some
previous knowledge, because I'd like to learn some of these prior concepts,
so that I can move through this process more smoothly?
[BD] I believe packstack will be supported. But, I already got
experience with manual set up
HA 3 Node (Active/Active) Controller ( Haproxy/Keepalived) . RH is
targeting RDO Manager
or TripleO with deploying to overcloud (Active/Passive) HA Controllers
(Pacemaker/Corosync).
At the point when RDO Manager (Triple0) will be used by everybody,
packstack won't be
needed at all.
Many thanks!
...John
On Tue, Feb 16, 2016 at 2:41 PM, Boris Derzhavets <bderzhavets(a)hotmail.com
> wrote:
>
>
>
> ------------------------------
> *From:* rdo-list-bounces(a)redhat.com <rdo-list-bounces(a)redhat.com> on
> behalf of John Alway <jalway(a)gmail.com>
> *Sent:* Tuesday, February 16, 2016 3:16 PM
> *To:* rdo-list(a)redhat.com
> *Subject:* [Rdo-list] The RDO Quickstart Guide and Private Network
>
> Hello,
>
> I overcame the problem of getting a valid key-pair value. I'm not sure
> exactly how it was fixed, but I found the rabbitmq server was down. This
> was a result of a host name conflict. The /etc/hostname and /etc/hosts
> files must both have the same hostname. I fixed that, and key-value pair
> now works. I'm not sure if that was the reason, because of some funny
> behavior prior, and it didn't initially complain about this. Suffice to
> say, I'm glad it's working!
>
> Anyway, I'm doing the first tutorial, and I've run into an issue.
>
> Here is the tutorial:
>
https://www.rdoproject.org/install/running-an-instance/
> <
https://www.rdoproject.org/install/running-an-instance/>
> Running an instance — RDO
> <
https://www.rdoproject.org/install/running-an-instance/>
>
www.rdoproject.org
> Running an Instance Step 1: Visit the Dashboard. Log in to the Openstack
> dashboard at
http://CONTROL_NODE/dashboard - the username is "demo". The
> password can be ...
>
>
> I ran through the steps, and when I got to Step 5, it wanted me to select
> a "private network," however I only have a public network to select.
>
> [BD]
>
> Create demo_network under particular user belongs to tenant "demo" (
> whose login has been used )
> demo_network should have interface attached to router, created by same
> user ( ACTIVE State )
> and having external gateway to public.
> Then in dropdown menu will appear just created demo_network. If you
> select it ( with correct DNS server
> been defined ) then VM supposed to be launched ( say CirrOS 3.4) will
> get Internet outbound connectivity.
> As soon as you assign floating IP from public pool VM will get inbound
> connectivity.
>
> I'm running this thing to get myself started, so that I can learn
> Openstack. So, I'm not sure why there is no private network, nor how I can
> create one.
>
> [BD]
> Network may be created via dashboard GUI right here . Maybe be created
> via Neutron CLI with corresponding credentials been sourced previously (#
> . keystonerc_user )
>
> Does anyone have any ideas on this?
>
> Thanks!
> ...John
>