[Rdo-list] Consequences for RDO of the proposal "no longer doing stable point releases"
by Jan van Eldik
Hi,
At the risk of fragmenting the upstream discussion: what would be the
consequences for RDO of the proposal to no longer provide stable
point releases?
From our consumer perspective, the RPMs following these stable point
releases have always allowed us to plan our upgrades in a
straightforward way:
- We ignore the initial release :)
- The first point release is the basis for our upgrade campaign,
where we upgrade component-by-component over a period of a
few months.
- The deployment of the subsequent point releases is a (usually)
trivial matter.
I would imagine that other deployers follow similar scenarios.
I think it would be good if RPMs would continue to be produced on
a regular basis, to allow consumers to benefit from the upstream
bug fixes. But I guess we would need to find a balance between
consumer needs and the available packaging effort.
Thoughts?
thanks, cheers, Jan
9 years, 5 months
[Rdo-list] [meeting] RDO packaging meeting minutes (2015-06-03)
by Alan Pevec
========================================
#rdo: RDO packaging meeting (2015-06-03)
========================================
Meeting started by apevec at 15:03:16 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/rdo/2015-06-03/rdo.2015-06-03-15.03.log....
.
Meeting summary
---------------
* roll call (apevec, 15:03:36)
* Post Kilo retrospective
https://trello.com/c/oGSEYj8J/53-post-kilo-retrospective (apevec,
15:06:04)
* we need better planing (apevec, 15:07:09)
* ACTION: apevec to expand master packaging add-new-package procedure
(apevec, 15:08:33)
* LINK:
https://www.rdoproject.org/packaging/rdo-packaging.html#_how_to_add_a_new...
(apevec, 15:09:05)
* CentOS SIGs side is sorting out publishing pipeline (apevec,
15:21:14)
* LINK: http://rdo.fedorapeople.org/rdo-release.rpm (cucumber_,
15:33:31)
* Kilo bootstrap repo was bad combination of Juno and new deps in RDO
Kilo GA location (apevec, 15:43:03)
* ACTION: apevec to start Liberty bootstrap with new deps in _testing_
location (apevec, 15:43:24)
* Changes in packaging which required changes in the Puppet module...
(apevec, 15:46:10)
* packaging changes must keep backward compatibility (apevec,
15:48:39)
* Improving reviewing process (apevec, 16:03:10)
* Identifying maintainers for every component (apevec, 16:04:50)
* delorean/master stopped or stuck (apevec, 16:05:54)
* delorean notification (apevec, 16:06:54)
* Delorean Trunk worked fine (we it was working) (apevec, 16:08:02)
* and last but not least: More community participation <3 (apevec,
16:08:31)
* open floor (apevec, 16:09:11)
Meeting ended at 16:19:05 UTC.
Action Items
------------
* apevec to expand master packaging add-new-package procedure
* apevec to start Liberty bootstrap with new deps in _testing_ location
Action Items, by person
-----------------------
* apevec
* apevec to expand master packaging add-new-package procedure
* apevec to start Liberty bootstrap with new deps in _testing_
location
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* apevec (187)
* number80 (55)
* jruzicka (44)
* mburned (35)
* kashyap (12)
* jpena (10)
* gchamoul (10)
* rbowen (9)
* cucumber_ (6)
* zodbot (4)
* ryansb (3)
* shardy (3)
* eggmaster (3)
* trown (3)
* jschlueter (2)
* chandankumar (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
9 years, 5 months
Re: [Rdo-list] RDO with existing external network
by Miguel Angel Ajo
Check this guide:
https://www.rdoproject.org/Networking_in_too_much_detail
Around “Neutron host: Router (M,N)” it may give you hints on how to debug the virtual routers… those are the ones which should be exposing your FIPs
could you also dump:
# neutron net-show external_network ?
--
Miguel Ángel Ajo
On Friday 5 June 2015 at 17:20, Maarten Hoes wrote:
> Hi,
>
>
> Yes I can ping 192.168.178.23.
>
> Ive added the rules with the dashboard/horizon.
>
> - Maarten
>
>
> On Fri, Jun 5, 2015 at 5:14 PM, Miguel Angel Ajo <mangelajo(a)redhat.com (mailto:mangelajo@redhat.com)> wrote:
> > It looks good.
> >
> > Can you ping 192.168.178.23 from your local network?
> >
> > I’d verify that the security groups allow ingress to ssh / ping or whatever you want to open.
> >
> > https://www.rdoproject.org/Running_an_instance_with_Neutron (Step 2) as keystonrc_admin
> >
> > --
> > Miguel Angel Ajo
> > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> >
> >
> > On Friday 5 June 2015 at 17:11, Maarten Hoes wrote:
> >
> > > Hi,
> > >
> > >
> > > Here they are.
> > >
> > >
> > > - Maarten
> > >
> > >
> > >
> > > On Fri, Jun 5, 2015 at 5:04 PM, Miguel Angel Ajo <mangelajo(a)redhat.com (mailto:mangelajo@redhat.com)> wrote:
> > > > Hmm :)
> > > >
> > > > Ok, can you post the output of:
> > > >
> > > > ovs-vsctl show
> > > >
> > > > ip addr
> > > >
> > > > ip link
> > > >
> > > > and the /etc/sysconfig/network-script/ files ?
> > > >
> > > > Best,
> > > > Miguel Ángel
> > > >
> > > >
> > > >
> > > >
> > > > On Friday 5 June 2015 at 17:01, Maarten Hoes wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > >
> > > > > 192.168.178.0/24 (http://192.168.178.0/24) is the local network provided by my cable isp box. 192.168.178.23 is my vmware vm im running linux (and openstack) on. Other devices in the same range are ping-able from within that vm.
> > > > >
> > > > >
> > > > > - Maarten
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Jun 5, 2015 at 4:55 PM, Miguel Angel Ajo <mangelajo(a)redhat.com (mailto:mangelajo@redhat.com)> wrote:
> > > > > > Hmm “no route to host” indicates that the machine were you’re running
> > > > > > ping or ssh has no route to 192.168.178.xx .
> > > > > >
> > > > > > That’s something specific to your setup.
> > > > > >
> > > > > > Is that subnet connected to one of the interfaces of your machine or has routing to reach it?
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Miguel Angel Ajo
> > > > > > Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
> > > > > >
> > > > > >
> > > > > > On Friday 5 June 2015 at 16:53, Maarten Hoes wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > >
> > > > > > > Thanks again for the update and effort.
> > > > > > >
> > > > > > > The guide works (produces no errors), but ...
> > > > > > >
> > > > > > > When I try to connect to the launched instance with either ping or ssh, I get these errors:
> > > > > > >
> > > > > > > # ping 192.168.178.52
> > > > > > > PING 192.168.178.52 (192.168.178.52) 56(84) bytes of data.
> > > > > > > From 192.168.178.23 icmp_seq=1 Destination Host Unreachable
> > > > > > >
> > > > > > > # ssh 192.168.178.52
> > > > > > > ssh: connect to host 192.168.178.52 port 22: No route to host
> > > > > > >
> > > > > > > I guess it has something to do with my setup ?
> > > > > > >
> > > > > > >
> > > > > > > - Maarten
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Jun 5, 2015 at 4:08 PM, Miguel Angel Ajo <mangelajo(a)redhat.com (mailto:mangelajo@redhat.com)> wrote:
> > > > > > > > Could you try now?,
> > > > > > > >
> > > > > > > > https://www.rdoproject.org/Neutron_with_existing_external_network
> > > > > > > >
> > > > > > > > Let me know if it works for you, here it does work.
> > > > > > > >
> > > > > > > > On Friday 5 June 2015 at 15:36, Maarten Hoes wrote:
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Thanks, that would be great.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > - Maarten
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Jun 5, 2015 at 3:17 PM, Miguel Angel Ajo <mangelajo(a)redhat.com (mailto:mangelajo@redhat.com)> wrote:
> > > > > > > > > > It’s a bit rusty,
> > > > > > > > > >
> > > > > > > > > > I’m working in an updated version,
> > > > > > > > > >
> > > > > > > > > > To start, I want to remove replication from the quickstart guide, so I’ll add a reference to Steps 1-2 from there, and then separate steps from there.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Miguel Angel Ajo
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Thursday 4 June 2015 at 13:57, Maarten Hoes wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi,
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > (like asked on irc)
> > > > > > > > > > >
> > > > > > > > > > > Im struggling with getting RDO to work with my existing network. Ive tried to follow this guide:
> > > > > > > > > > >
> > > > > > > > > > > https://www.rdoproject.org/Neutron_with_existing_external_network
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > But cant seem to get it to work for me. Could you take a look at that guide and see if its still accurate ?
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > - Maarten Hoes.
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
9 years, 5 months
Re: [Rdo-list] RDO with existing external network
by Miguel Angel Ajo
It’s a bit rusty,
I’m working in an updated version,
To start, I want to remove replication from the quickstart guide, so I’ll add a reference to Steps 1-2 from there, and then separate steps from there.
--
Miguel Angel Ajo
On Thursday 4 June 2015 at 13:57, Maarten Hoes wrote:
> Hi,
>
>
> (like asked on irc)
>
> Im struggling with getting RDO to work with my existing network. Ive tried to follow this guide:
>
> https://www.rdoproject.org/Neutron_with_existing_external_network
>
>
> But cant seem to get it to work for me. Could you take a look at that guide and see if its still accurate ?
>
>
>
> Thanks,
>
>
>
> - Maarten Hoes.
>
9 years, 5 months
[Rdo-list] Cloud SIG meeting minutes (2015-06-04)
by Rich Bowen
Thanks to those that attended the Cloud SIG Meeting. Minutes follow.
Minutes may also be found online at:
http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.txt
http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.html
Full logs may be found at:
http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.log.html
http://centos.org/minutes/2015/june/centos-devel.2015-06-04-15.00.log.txt
=====================
#centos-devel Meeting
=====================
Meeting started by rbowen at 15:00:53 UTC. The full logs are available
at centos-devel/2015/centos-devel.2015-06-04-15.00.log.html .
Meeting summary
---------------
* LINK: https://etherpad.openstack.org/p/cloud_sig_agenda (rbowen,
15:01:05)
* rollcall (rbowen, 15:01:16)
* Update on Juno/Kilo releases (rbowen, 15:04:19)
* GSOC updates (rbowen, 15:06:03)
* My project is related to atomic, fedora and centOS (tmrts,
15:07:43)
* LINK: https://github.com/TamerTas/cloud-init/blob/master/ROADMAP.md
(tmrts, 15:08:38)
* First few weeks I'll be focusing on the core part of the cloud-init
(users, network, ssh, custom scripts) then I'll get to the specifics
of each target system (tmrts, 15:09:37)
* Open Floor (rbowen, 15:17:22)
* ACTION: I'll add CentOS 6 to the cloud-init test environment
(tmrts, 15:22:26)
Meeting ended at 15:28:31 UTC.
Action Items
------------
* I'll add CentOS 6 to the cloud-init test environment
Action Items, by person
-----------------------
* **UNASSIGNED**
* I'll add CentOS 6 to the cloud-init test environment
People Present (lines said)
---------------------------
* rbowen (33)
* kbsingh (19)
* tmrts (17)
* apevec (6)
* centbot (2)
* number80 (2)
* alphacc (1)
* Evolution (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://rdoproject.org/
9 years, 5 months
[Rdo-list] GRE traffic in openstack
by ICHIBA Sara
Hey there,
I have to set a GRE tunnel between VM1 deployed on top of Openstack and a
physical server. I was wondering in this case How can I proceed. Can I do
it the classic way by providing my VM1 with a floating ip and just set the
tunnel as normal? by the way my ovs uses vxlan and not gre tunnel? Do you
have any idea?
In advance, thanks for your response.
Sara
9 years, 5 months
[Rdo-list] Neutron with existing network issues.
by NS Murthy
Hi
I am new to RDO openstack. I have installed in one single bare metal server which had 2 NICS connected with different subnets on my company network.
1) Primary NIC subnet: 10.58.100.24 - This is where i have installed openstack and openstack dashboard is listening to logon from this IP.2) Tenant NIC subnet: 10.68.200.5 - this is a secondary IP which i kept for tenant network so that i can logon.3) 1 br-ex interface ip 10.58.100.24
I have used br-ex interface address(which is my primary 1GB NIC IP) configured for tenant however i cannot ping tenant instance ip 10.68.200.25 from my management node but can ping floating IPs(10.58.100.25) and can do SSH to floating ip.
can someone provide a tip or help how to ping tenant IP as well connect to tenant IP without floating IP.
At the end i need the below.1) i need to have tenant network on 10.68.200.0/24, i need to ping this network so that tenant can logon to SSH without floating IP.2) i have requirement to have 2 Network interfaces on a instance ? how do i accomplish this ? becasue every tenant have fense network so i can only get one network when i spin instance from image ?
BR,Murthy
I
9 years, 5 months
Re: [Rdo-list] autoscaling.yaml template
by ICHIBA Sara
If you see the biginning of the cloud ini: you 'll find out that i
configured a wordpress repo on a web server: 192.168.5.105/repos/wordpress.
and normaly my vm should download the packages from that repos. But, I
don't know why it doesn't
>
> Towards the end of the log is the following:
>
> cloud-init[922]: No package wordpress available.
>
> The main Fedora repository includes wordpress, but the CentOS one does
> not. You will either need to add the CentOS EPEL repository in your boot
> script, or switch to a Fedora cloud image.
>
>
>
> On 03/06/15 08:06, ICHIBA Sara wrote:
> > Hello there,
> >
> > Lately i was trying to make work the autoscaling.yaml template. So I
> > installed a web server and uploaded the wordpress repo . when I launch
> > my template with heat, and take a look at the log of the web server
> > and the db server launched with heat I found these errors. Can you
> > tell me what I can do to fix them? below the logs and attached the
> > temmplate I use
> >
> > ====> database server log
> > cloud-init[728]: Cloud-init v. 0.7.5 running 'init' at Tue, 02 Jun 2015
> 15:47:39 +0000. Up 9.78 seconds.
> > cloud-init[728]: ci-info: +++++++++++++++++++++++++Net device
> info++++++++++++++++++++++++++
> > cloud-init[728]: ci-info:
> +--------+------+------------+---------------+-------------------+
> > cloud-init[728]: ci-info: | Device | Up | Address | Mask
> | Hw-Address |
> > cloud-init[728]: ci-info:
> +--------+------+------------+---------------+-------------------+
> > cloud-init[728]: ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0
> | . |
> > cloud-init[728]: ci-info: | eth0: | True | 20.0.0.169 | 255.255.255.0 |
> fa:16:3e:f3:f2:25 |
> > cloud-init[728]: ci-info:
> +--------+------+------------+---------------+-------------------+
> > cloud-init[728]: ci-info: ++++++++++++++++++++++++++++++Route
> info++++++++++++++++++++++++++++++
> > cloud-init[728]: ci-info:
> +-------+-------------+----------+---------------+-----------+-------+
> > cloud-init[728]: ci-info: | Route | Destination | Gateway | Genmask
> | Interface | Flags |
> > cloud-init[728]: ci-info:
> +-------+-------------+----------+---------------+-----------+-------+
> > cloud-init[728]: ci-info: | 0 | 0.0.0.0 | 20.0.0.1 | 0.0.0.0
> | eth0 | UG |
> > cloud-init[728]: ci-info: | 1 | 20.0.0.0 | 0.0.0.0 |
> 255.255.255.0 | eth0 | U |
> > cloud-init[728]: ci-info:
> +-------+-------------+----------+---------------+-----------+-------+
> >
> > CentOS Linux 7 (Core)
> > Kernel 3.10.0-229.el7.x86_64 on an x86_64
> >
> > host-20-0-0-169 login: cloud-init[901]: Cloud-init v. 0.7.5 running
> 'modules:config' at Tue, 02 Jun 2015 15:47:44 +0000. Up 15.32 seconds.
> > cloud-init[922]: Cloud-init v. 0.7.5 running 'modules:final' at Tue, 02
> Jun 2015 15:47:45 +0000. Up 15.87 seconds.
> > cloud-init[922]: #!/bin/bash -v
> > cloud-init[922]: cat << EOF > /etc/resolv.conf
> > cloud-init[922]: nameserver 8.8.8.8
> > cloud-init[922]: EOF
> > cloud-init[922]: yum -y install firewalld
> > cloud-init[922]: Loaded plugins: fastestmirror
> > cloud-init[922]: Determining fastest mirrors
> > cloud-init[922]: * base:centos.quelquesmots.fr <
> http://centos.quelquesmots.fr/>
> > cloud-init[922]: * extras:centos.mirrors.ovh.net <
> http://centos.mirrors.ovh.net/>
> > cloud-init[922]: * updates:centos.quelquesmots.fr <
> http://centos.quelquesmots.fr/>
> > cloud-init[922]: Resolving Dependencies
> > cloud-init[922]: --> Running transaction check
> > cloud-init[922]: ---> Package firewalld.noarch 0:0.3.9-11.el7 will be
> installed
> > cloud-init[922]: --> Processing Dependency: python-slip-dbus for
> package: firewalld-0.3.9-11.el7.noarch
> > cloud-init[922]: --> Processing Dependency: ebtables for package:
> firewalld-0.3.9-11.el7.noarch
> > cloud-init[922]: --> Running transaction check
> > cloud-init[922]: ---> Package ebtables.x86_64 0:2.0.10-13.el7 will be
> installed
> > cloud-init[922]: ---> Package python-slip-dbus.noarch 0:0.4.0-2.el7 will
> be installed
> > cloud-init[922]: --> Processing Dependency: python-slip = 0.4.0-2.el7
> for package: python-slip-dbus-0.4.0-2.el7.noarch
> > cloud-init[922]: --> Running transaction check
> > cloud-init[922]: ---> Package python-slip.noarch 0:0.4.0-2.el7 will be
> installed
> > cloud-init[922]: --> Finished Dependency Resolution
> > cloud-init[922]: Dependencies Resolved
> > cloud-init[922]:
> ================================================================================
> > cloud-init[922]: Package Arch Version
> Repository Size
> > cloud-init[922]:
> ================================================================================
> > cloud-init[922]: Installing:
> > cloud-init[922]: firewalld noarch 0.3.9-11.el7
> base 465 k
> > cloud-init[922]: Installing for dependencies:
> > cloud-init[922]: ebtables x86_64 2.0.10-13.el7
> base 122 k
> > cloud-init[922]: python-slip noarch 0.4.0-2.el7
> base 30 k
> > cloud-init[922]: python-slip-dbus noarch 0.4.0-2.el7
> base 31 k
> > cloud-init[922]: Transaction Summary
> > cloud-init[922]:
> ================================================================================
> > cloud-init[922]: Install 1 Package (+3 Dependent packages)
> > cloud-init[922]: Total download size: 649 k
> > cloud-init[922]: Installed size: 2.8 M
> > cloud-init[922]: Downloading packages:
> > cloud-init[922]: warning:
> /var/cache/yum/x86_64/7/base/packages/python-slip-0.4.0-2.el7.noarch.rpm:
> Header V3 RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
> > cloud-init[922]: Public key for python-slip-0.4.0-2.el7.noarch.rpm is
> not installed
> > cloud-init[922]:
> --------------------------------------------------------------------------------
> > cloud-init[922]: Total 462
> kB/s | 649 kB 00:01
> > cloud-init[922]: Retrieving key from
> file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
> > cloud-init[922]: Importing GPG key 0xF4A80EB5:
> > cloud-init[922]: Userid : "CentOS-7 Key (CentOS 7 Official Signing
> Key) <security(a)centos.org <mailto:security@centos.org>>"
> > cloud-init[922]: Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7
> f4a8 0eb5
> > cloud-init[922]: Package :
> centos-release-7-1.1503.el7.centos.2.7.x86_64 (installed)
> > cloud-init[922]: From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
> > cloud-init[922]: Running transaction check
> > cloud-init[922]: Running transaction test
> > cloud-init[922]: Transaction test succeeded
> > cloud-init[922]: Running transaction
> > cloud-init[922]: Installing : python-slip-0.4.0-2.el7.noarch
> 1/4
> > cloud-init[922]: Installing : python-slip-dbus-0.4.0-2.el7.noarch
> 2/4
> > cloud-init[922]: Installing : ebtables-2.0.10-13.el7.x86_64
> 3/4
> > cloud-init[922]: Installing : firewalld-0.3.9-11.el7.noarch
> 4/4
> > cloud-init[922]: Verifying : firewalld-0.3.9-11.el7.noarch
> 1/4
> > cloud-init[922]: Verifying : python-slip-dbus-0.4.0-2.el7.noarch
> 2/4
> > cloud-init[922]: Verifying : ebtables-2.0.10-13.el7.x86_64
> 3/4
> > cloud-init[922]: Verifying : python-slip-0.4.0-2.el7.noarch
> 4/4
> > cloud-init[922]: Installed:
> > cloud-init[922]: firewalld.noarch 0:0.3.9-11.el7
> > cloud-init[922]: Dependency Installed:
> > cloud-init[922]: ebtables.x86_64 0:2.0.10-13.el7
> python-slip.noarch 0:0.4.0-2.el7
> > cloud-init[922]: python-slip-dbus.noarch 0:0.4.0-2.el7
> > cloud-init[922]: Complete!
> > cloud-init[922]: systemctl start firewalld
> > Starting firewalld - dynamic firewall daemon...
> > [ 37.378596] ip_tables: (C) 2000-2006 Netfilter Core Team
> > [ 37.429522] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> > [ 37.491387] ip6_tables: (C) 2000-2006 Netfilter Core Team
> > [ 37.539733] Ebtables v2.0 registered
> > [ 37.572087] Bridge firewalling registered
> > [[32m OK [0m] Started firewalld - dynamic firewall daemon.
> > cloud-init[922]: systemctl enable firewalld
> > cloud-init[922]: firewall-cmd --permanent --add-port=3306/tcp
> > [ 40.564139] Adjusting kvm-clock more than 11% (9437184 vs 9311354)
> > cloud-init[922]: ERROR:dbus.proxies:Introspect error on
> :1.6:/org/fedoraproject/FirewallD1: dbus.exceptions.DBusException:
> org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible
> causes include: the remote application did not send a reply, the message
> bus security policy blocked the reply, the reply timeout expired, or the
> network connection was broken.
> > Starting Authorization Manager...
> > [[32m OK [0m] Started Authorization Manager.
> > [[32m OK [0m] Created slice user-0.slice.
> > Starting Cleanup of Temporary Directories...
> > [[32m OK [0m] Started Cleanup of Temporary Directories.
> > ===>web-server log
> > cloud-init[728]: Cloud-init v. 0.7.5 running 'init' at Tue, 02 Jun 2015
> 16:01:42 +0000. Up 12.17 seconds.
> > cloud-init[728]: ci-info: +++++++++++++++++++++++++Net device
> info++++++++++++++++++++++++++
> > cloud-init[728]: ci-info:
> +--------+------+------------+---------------+-------------------+
> > cloud-init[728]: ci-info: | Device | Up | Address | Mask
> | Hw-Address |
> > cloud-init[728]: ci-info:
> +--------+------+------------+---------------+-------------------+
> > cloud-init[728]: ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0
> | . |
> > cloud-init[728]: ci-info: | eth0: | True | 20.0.0.172 | 255.255.255.0 |
> fa:16:3e:61:e9:0e |
> > cloud-init[728]: ci-info:
> +--------+------+------------+---------------+-------------------+
> > cloud-init[728]: ci-info: ++++++++++++++++++++++++++++++Route
> info++++++++++++++++++++++++++++++
> > cloud-init[728]: ci-info:
> +-------+-------------+----------+---------------+-----------+-------+
> > cloud-init[728]: ci-info: | Route | Destination | Gateway | Genmask
> | Interface | Flags |
> > cloud-init[728]: ci-info:
> +-------+-------------+----------+---------------+-----------+-------+
> > cloud-init[728]: ci-info: | 0 | 0.0.0.0 | 20.0.0.1 | 0.0.0.0
> | eth0 | UG |
> > cloud-init[728]: ci-info: | 1 | 20.0.0.0 | 0.0.0.0 |
> 255.255.255.0 | eth0 | U |
> > cloud-init[728]: ci-info:
> +-------+-------------+----------+---------------+-----------+-------+
> >
> > CentOS Linux 7 (Core)
> > Kernel 3.10.0-229.el7.x86_64 on an x86_64
> >
> > host-20-0-0-172 login: cloud-init[901]: Cloud-init v. 0.7.5 running
> 'modules:config' at Tue, 02 Jun 2015 16:01:47 +0000. Up 16.92 seconds.
> > cloud-init[922]: Cloud-init v. 0.7.5 running 'modules:final' at Tue, 02
> Jun 2015 16:01:47 +0000. Up 17.53 seconds.
> > cloud-init[922]: #!/bin/bash -v
> > cloud-init[922]: cat << EOF > /etc/resolv.conf
> > cloud-init[922]: nameserver 8.8.8.8
> > cloud-init[922]: EOF
> > cloud-init[922]: yum -y install firewalld
> > cloud-init[922]: systemctl start firewalld
> > cloud-init[922]: systemctl enable firewalld
> > cloud-init[922]: firewall-cmd --permanent --add-port=3306/tcp
> > cloud-init[922]: firewall-cmd --permanent --add-port=80/tcp
> > cloud-init[922]: firewall-cmd --permanent --add-port=443/tcp
> > cloud-init[922]: firewall-cmd --reload
> > cloud-init[922]: cat << EOF >> /etc/yum.repos.d/rhel.repo
> > cloud-init[922]: [rhel-7-server-rpms]
> > cloud-init[922]: name=rhel-7-server-rpms
> > cloud-init[922]: baseurl=http://172.16.0.129:81/repos/rhel-7-server-rpms
> > cloud-init[922] <
> http://172.16.0.129:81/repos/rhel-7-server-rpmscloud-init%5B922%5D>:
> gpgcheck=0
> > cloud-init[922]: enabled=1
> > cloud-init[922]: [wordpress]
> > cloud-init[922]: name=wordpress
> > cloud-init[922]: baseurl=http://192.168.5.105:80/repos/wordpress
> > cloud-init[922] <
> http://192.168.5.105:80/repos/wordpresscloud-init%5B922%5D>: gpgcheck=0
> > cloud-init[922]: enabled=1
> > cloud-init[922]: EOF
> > cloud-init[922]: yum -y install httpd wordpress
> > cloud-init[922]: Loaded plugins: fastestmirror
> > cloud-init[922]: Determining fastest mirrors
> > cloud-init[922]: * base:centos.crazyfrogs.org <
> http://centos.crazyfrogs.org>
> > cloud-init[922]: * extras:centos.crazyfrogs.org <
> http://centos.crazyfrogs.org>
> > cloud-init[922]: * updates:centos.crazyfrogs.org <
> http://centos.crazyfrogs.org>
> > cloud-init[922]: No package wordpress available.
> > cloud-init[922]: Resolving Dependencies
> > cloud-init[922]: --> Running transaction check
> > cloud-init[922]: ---> Package httpd.x86_64 0:2.4.6-31.el7.centos will be
> installed
> > cloud-init[922]: --> Processing Dependency: httpd-tools =
> 2.4.6-31.el7.centos for package: httpd-2.4.6-31.el7.centos.x86_64
> > cloud-init[922]: --> Processing Dependency: /etc/mime.types for package:
> httpd-2.4.6-31.el7.centos.x86_64
> > cloud-init[922]: --> Processing Dependency: libaprutil-1.so.0()(64bit)
> for package: httpd-2.4.6-31.el7.centos.x86_64
> > cloud-init[922]: --> Processing Dependency: libapr-1.so.0()(64bit) for
> package: httpd-2.4.6-31.el7.centos.x86_64
> > cloud-init[922]: --> Running transaction check
> > cloud-init[922]: ---> Package apr.x86_64 0:1.4.8-3.el7 will be installed
> > cloud-init[922]: ---> Package apr-util.x86_64 0:1.5.2-6.el7 will be
> installed
> > cloud-init[922]: ---> Package httpd-tools.x86_64 0:2.4.6-31.el7.centos
> will be installed
> > cloud-init[922]: ---> Package mailcap.noarch 0:2.1.41-2.el7 will be
> installed
> > cloud-init[922]: --> Finished Dependency Resolution
> > cloud-init[922]: Dependencies Resolved
> > cloud-init[922]:
> ================================================================================
> > cloud-init[922]: Package Arch Version
> Repository Size
> > cloud-init[922]:
> ================================================================================
> > cloud-init[922]: Installing:
> > cloud-init[922]: httpd x86_64 2.4.6-31.el7.centos
> base 2.7 M
> > cloud-init[922]: Installing for dependencies:
> > cloud-init[922]: apr x86_64 1.4.8-3.el7
> base 103 k
> > cloud-init[922]: apr-util x86_64 1.5.2-6.el7
> base 92 k
> > cloud-init[922]: httpd-tools x86_64 2.4.6-31.el7.centos
> base 79 k
> > cloud-init[922]: mailcap noarch 2.1.41-2.el7
> base 31 k
> > cloud-init[922]: Transaction Summary
> > cloud-init[922]:
> ================================================================================
> > cloud-init[922]: Install 1 Package (+4 Dependent packages)
> > cloud-init[922]: Total download size: 3.0 M
> > cloud-init[922]: Installed size: 10 M
> > cloud-init[922]: Downloading packages:
> > cloud-init[922]: warning:
> /var/cache/yum/x86_64/7/base/packages/apr-1.4.8-3.el7.x86_64.rpm: Header V3
> RSA/SHA256 Signature, key ID f4a80eb5: NOKEY
> > cloud-init[922]: Public key for apr-1.4.8-3.el7.x86_64.rpm is not
> installed
> > cloud-init[922]:
> --------------------------------------------------------------------------------
> > cloud-init[922]: Total 949
> kB/s | 3.0 MB 00:03
> > cloud-init[922]: Retrieving key from
> file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
> > cloud-init[922]: Importing GPG key 0xF4A80EB5:
> > cloud-init[922]: Userid : "CentOS-7 Key (CentOS 7 Official Signing
> Key) <security(a)centos.org <mailto:security@centos.org>>"
> > cloud-init[922]: Fingerprint: 6341 ab27 53d7 8a78 a7c2 7bb1 24c6 a8a7
> f4a8 0eb5
> > cloud-init[922]: Package :
> centos-release-7-1.1503.el7.centos.2.7.x86_64 (installed)
> > cloud-init[922]: From : /etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
> > cloud-init[922]: Running transaction check
> > cloud-init[922]: Running transaction test
> > cloud-init[922]: Transaction test succeeded
> > cloud-init[922]: Running transaction
> > cloud-init[922]: Installing : apr-1.4.8-3.el7.x86_64
> 1/5
> > cloud-init[922]: Installing : apr-util-1.5.2-6.el7.x86_64
> 2/5
> > cloud-init[922]: Installing : httpd-tools-2.4.6-31.el7.centos.x86_64
> 3/5
> > cloud-init[922]: Installing : mailcap-2.1.41-2.el7.noarch
> 4/5
> > cloud-init[922]: Installing : httpd-2.4.6-31.el7.centos.x86_64
> 5/5
> > cloud-init[922]: Verifying : httpd-tools-2.4.6-31.el7.centos.x86_64
> 1/5
> > cloud-init[922]: Verifying : apr-1.4.8-3.el7.x86_64
> 2/5
> > cloud-init[922]: Verifying : mailcap-2.1.41-2.el7.noarch
> 3/5
> > cloud-init[922]: Verifying : httpd-2.4.6-31.el7.centos.x86_64
> 4/5
> > cloud-init[922]: Verifying : apr-util-1.5.2-6.el7.x86_64
> 5/5
> > cloud-init[922]: Installed:
> > cloud-init[922]: httpd.x86_64 0:2.4.6-31.el7.centos
> > cloud-init[922]: Dependency Installed:
> > cloud-init[922]: apr.x86_64 0:1.4.8-3.el7
> apr-util.x86_64 0:1.5.2-6.el7
> > cloud-init[922]: httpd-tools.x86_64 0:2.4.6-31.el7.centos
> mailcap.noarch 0:2.1.41-2.el7
> > cloud-init[922]: Complete!
> > cloud-init[922]: systemctl start httpd.service
> > Starting The Apache HTTP Server...
> > [[32m OK [0m] Started The Apache HTTP Server.
> > cloud-init[922]: systemctl enable httpd.service
> > cloud-init[922]: ln -s '/usr/lib/systemd/system/httpd.service'
> '/etc/systemd/system/multi-user.target.wants/httpd.service'
> > cloud-init[922]: setsebool -P httpd_can_network_connect_db=1
> > cloud-init[922]: sed -i "/Deny from All/d"
> /etc/httpd/conf.d/wordpress.conf
> > cloud-init[922]: sed: can't read /etc/httpd/conf.d/wordpress.conf: No
> such file or directory
> > cloud-init[922]: sed -i "s/Require local/Require all granted/"
> /etc/httpd/conf.d/wordpress.conf
> > cloud-init[922]: sed: can't read /etc/httpd/conf.d/wordpress.conf: No
> such file or directory
> > cloud-init[922]: sed -i s/database_name_here/wordpress/
> /etc/wordpress/wp-config.php
> > cloud-init[922]: sed: can't read /etc/wordpress/wp-config.php: No such
> file or directory
> > cloud-init[922]: sed -i s/username_here/wordpress/
> /etc/wordpress/wp-config.php
> > cloud-init[922]: sed: can't read /etc/wordpress/wp-config.php: No such
> file or directory
> > cloud-init[922]: sed -i
> s/password_here/GJM76RbvIje4C7eh2aOdlQQedqvxjBH2/
> /etc/wordpress/wp-config.php
> > cloud-init[922]: sed: can't read /etc/wordpress/wp-config.php: No such
> file or directory
> > cloud-init[922]: sed -i s/localhost/20.0.0.68/ <http://20.0.0.68/>
> /etc/wordpress/wp-config.php
> > cloud-init[922]: sed: can't read /etc/wordpress/wp-config.php: No such
> file or directory
> > cloud-init[922]: systemctl restart httpd.service
> > Stopping The Apache HTTP Server...
> > [[32m OK [0m] Stopped The Apache HTTP Server.
> > Starting The Apache HTTP Server...
> > [[32m OK [0m] Started The Apache HTTP Server.
> > ci-info: ++++++++++Authorized keys from
> /home/centos/.ssh/authorized_keys for user centos+++++++++++
> > ci-info:
> +---------+-------------------------------------------------+---------+-------------------+
> > ci-info: | Keytype | Fingerprint (md5) |
> Options | Comment |
> > ci-info:
> +---------+-------------------------------------------------+---------+-------------------+
> > ci-info: | ssh-rsa | 2d:b8:76:2f:ab:f5:f1:72:f8:75:46:00:f9:d3:24:60 |
> - | Generated-by-Nova |
> > ci-info:
> +---------+-------------------------------------------------+---------+-------------------+
> > ec2:
> > ec2: #############################################################
> > ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
> > ec2: 256 88:ab:b1:ac:08:d9:70:41:f2:04:14:a3:1a:4d:02:fe (ECDSA)
> > ec2: 256 0e:3e:9b:d5:4b:cb:c9:78:c7:99:a4:bf:05:0d:7a:a8 (ED25519)
> > ec2: 2048 f2:f8:e5:70:d1:f4:f0:57:ea:9c:d1:75:f3:75:17:22 (RSA)
> > ec2: -----END SSH HOST KEY FINGERPRINTS-----
> > ec2: #############################################################
> > -----BEGIN SSH HOST KEY KEYS-----
> > ecdsa-sha2-nistp256
> AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBCXquFpCyVkwLlWJ81GozEjViYP41EELARbVt5ISfsRCDNGk31bsGmgy7ecjg7g1LRtTxTs0OWJ3Hy2fZhio1KQ=
> > ssh-ed25519
> AAAAC3NzaC1lZDI1NTE5AAAAICORDKYmglupDLdv8Cj5ut14BpD65Grm8p0SQDifMans
> > ssh-rsa
> AAAAB3NzaC1yc2EAAAADAQABAAABAQDTQjdbT8OCAnmV5bbO/llks+2E26pajgS9ZortTLKOGQp9KmYMIq9CXjUWQjmn+vlFMPkyMk4DG9K/XDX3WRXgErNUpIsmJPUMOnoyxz4U+dYCOSm7pUfoyQphvqxGzkzC/UMwHYcakSpUssLUY85ZcoIz9HmaNTkiiHoJe/ezvjVrAAAcOViYL2qcOATf7MfNqkyqJlk65O7k5pf3+RFh9ta1rijubzaHfBZxKiQfVeJV61vwmF6tBONDOlC/BVSI+k/zg0Evsn+5uKPlhsoeB5uSr1DxTSdBYn3yrHcqceEtgh2uiwhS7prvU911KfRjkf+PwGvtDg9iLlAuJioV
> > -----END SSH HOST KEY KEYS-----
> > cloud-init[922]: Cloud-init v. 0.7.5 finished at Tue, 02 Jun 2015
> 16:02:31 +0000. Datasource DataSourceOpenStack [net,ver=2]. Up 60.92
> seconds
> > [[32m OK [0m] Started Execute cloud user/final scripts.
> > [[32m OK [0m] Reached target Multi-User System.
> >
> >
> >
> > _______________________________________________
> > Rdo-list mailing list
> > Rdo-list(a)redhat.com
> > https://www.redhat.com/mailman/listinfo/rdo-list
> >
> > To unsubscribe: rdo-list-unsubscribe(a)redhat.com
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://www.redhat.com/archives/rdo-list/attachments/20150603/b703d8c3/at...
> >
>
> ------------------------------
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list(a)redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
>
> End of Rdo-list Digest, Vol 27, Issue 4
> ***************************************
>
9 years, 5 months
