Thanks for the heads up re EL7, Marcus.
Looks like it needs more testing. Also in 7.1 (or 7.2?) they're going to 
upgrade the virt stack considerably, basically qemu-rhev from oVirt will 
obsolete current qemu-kvm, so who knows what changes this will bring; though 
overall changes should bring enhanced performance etc.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Marcus" <shadow...@gmail.com>
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 4 March, 2015 23:39:57
> Subject: Re: [VOTE] Apache CloudStack 4.5.0 RC4

> Yeah, it's not related to setting up mysql, it's that the java mysql
> library (as installed by CentOS 7) is not in the classpath. I added it
> to classpath in "/usr/sbin/tomcat" and things started working.
> 
> I think CentOS 7 support should be marked as 'tech preview' for 4.5.
> Here are some notes related to roadblocks that can be worked through:
> 
> MGMT SERVER:
>   * mysql-connector-java issue (to be fixed in point release, unless
> there's something in my setup procedure that caused it). Changed
> "build-classpath commons-daemon" to "build-classpath commons-daemon
> mysql-connector-java" in /usr/sbin/tomcat.
>   * java tendency to prefer listening only on ipv6 if present, though
> this is probably a general issue and not specific to CentOS7. Had to
> add "-Djava.net.preferIPv4Stack=true" to /usr/sbin/tomcat
>   * document firewalld setup changes for full release, as old
> instructions show iptables setup
> 
> AS HYPERVISOR:
>    * Disable consistent network device naming, agent supports only
> eth, bond, vlan, vx, and em network device names
>    * Document firewalld setup changes for full release
>    * Security groups and firewall support needs testing
>    * Systemd 'co-mounts' cpu,cpuacct cgroups, causes issues for
> launching a VM with libvirt. Need to edit /etc/systemd/system.conf and
> pass empty string to JoinControllers param. Then rebuild the initramfs
> via 'new-kernel-pkg --mkinitrd --install `uname -r`'. Perhaps there's
> a more elegant solution to this.
> 
> Other than this I'm +1 for this release on CentOS 6.5
> 
> On Wed, Mar 4, 2015 at 2:07 PM, Paul Angus <paul.an...@shapeblue.com> wrote:
>> Hi Marcus,
>>
>> To install and setup MySQL (5.6) for CentOS7 with ACS4.5
>>
>> I did the following:
>>
>> setenforce permissive
>> sed  -i "/^SELINUX=/ c\SELINUX=permissive" /etc/selinux/config
>> rpm -Uvh http://dev.mysql.com/get/mysql-community-release-el7-5.noarch.rpm
>> yum -y install mysql-community-server
>> sed -i -e '/datadir/ a\innodb_rollback_on_timeout=1' -e '/datadir/
>> a\innodb_lock_wait_timeout=600' -e '/datadir/ a\max_connections=350' -e
>> '/datadir/ a\log-bin=mysql-bin' -e "/datadir/ a\binlog-format = 'ROW'"
>> /etc/my.cnf
>> mysql_install_db --user=mysql --ldata=/var/lib/mysql
>> /usr/bin/systemctl enable mysqld
>> /usr/bin/systemctl start mysqld
>> /usr/bin/mysqladmin -u root password 'password'
>>
>> CloudStack then installed and worked ok.
>>
>> Regards,
>>
>> Paul Angus
>> Cloud Architect
>> D: +44 20 3468 5163 |S: +44 20 3603 0540 | M: +44 7711 418 784 | T: 
>> @CloudyAngus
>> paul.an...@shapeblue.com
>>
>> -----Original Message-----
>> From: Marcus [mailto:shadow...@gmail.com]
>> Sent: 04 March 2015 21:10
>> To: dev@cloudstack.apache.org
>> Subject: Re: [VOTE] Apache CloudStack 4.5.0 RC4
>>
>> I got past this by editing /usr/sbin/tomcat and adding mysql-connector-java 
>> to
>> classpath, but I'd be curious to hear from others who might be testing 
>> against
>> EL7 distros.
>>
>> On Wed, Mar 4, 2015 at 12:27 PM, Marcus <shadow...@gmail.com> wrote:
>>> I'm not voting yet, but I did have an issue with CentOS7. Not sure if
>>> we were intending to release 4.5 support for it.
>>>
>>> 2015-02-09 11:28:07,112 ERROR [c.c.u.d.Merovingian2]
>>> (localhost-startStop-1:null) Unable to get a new db connection
>>>
>>> java.sql.SQLException: No suitable driver found for
>>> jdbc:mysql://localhost:3306/cloud?autoReconnect=true&prepStmtCacheSize
>>> =517&cachePrepStmts=true
>>>
>>> mysql-connector-java is installed.
>>>
>>>
>>> On Wed, Mar 4, 2015 at 11:08 AM, Pierre-Luc Dion <pd...@cloudops.com> wrote:
>>>> +1 (binding)
>>>>
>>>> Did perform lot of tests against RC3, did upgrade from 4.4.2 to
>>>> 4.5-RC4, no issues so far.
>>>>
>>>> If this RC pass the vote, can we do the GA from with a different
>>>> commit ID to include the license header flagged by Chip ?
>>>>
>>>>
>>>> PL
>>>>
>>>>
>>>> On Wed, Mar 4, 2015 at 1:33 PM, Marcus <shadow...@gmail.com> wrote:
>>>>
>>>>> This looks like a config issue "host sent incorrect data center".
>>>>>
>>>>> From your subsequent emails, my guess is that this host was once
>>>>> added  to another zone '3' in your test environment, then re-added
>>>>> to the zone '5' without being explicitly removed from the zone '3'.
>>>>> There might be more info in the other columns of that table, as in
>>>>> date added and potentially removed.
>>>>>
>>>>> On Mon, Mar 2, 2015 at 10:55 AM, Nux! <n...@li.nux.ro> wrote:
>>>>> > Ok, didn't go so well. Frustrating, the previous RC worked.
>>>>> >
>>>>> > Not sure whether to -1 or not.
>>>>> >
>>>>> > One of my hosts is in Disconnected mode and the logs show:
>>>>> >
>>>>> > 2015-03-02 18:48:08,336 DEBUG [cloud.agent.Agent]
>>>>> (agentRequest-Handler-1:null) Processing command:
>>>>> com.cloud.agent.api.ReadyCommand
>>>>> > 2015-03-02 18:48:08,337 DEBUG [cloud.agent.Agent]
>>>>> > (Agent-Handler-2:null)
>>>>> Startup task cancelled
>>>>> > 2015-03-02 18:48:08,337 DEBUG [cloud.agent.Agent]
>>>>> (agentRequest-Handler-1:null) Not ready to connect to mgt server:
>>>>> java.lang.IllegalArgumentException: Host 192.168.203.66 sent
>>>>> incorrect data
>>>>> center: 1
>>>>> > 2015-03-02 18:48:08,337 INFO  [cloud.agent.Agent]
>>>>> > (Agent-Handler-2:null)
>>>>> Proccess agent startup answer, agent id = 0
>>>>> > 2015-03-02 18:48:08,337 INFO  [cloud.agent.Agent]
>>>>> > (Agent-Handler-2:null)
>>>>> Set agent id 0
>>>>> > 2015-03-02 18:48:08,338 INFO  [cloud.agent.Agent]
>>>>> (AgentShutdownThread:null) Stopping the agent: Reason = sig.kill
>>>>> > 2015-03-02 18:48:08,339 DEBUG [cloud.agent.Agent]
>>>>> (AgentShutdownThread:null) Sending shutdown to management server
>>>>> >
>>>>> > My other host seems to run just fine; though it has no running VMs.
>>>>> >
>>>>> > Thoughts?
>>>>> >
>>>>> > Lucian
>>>>> >
>>>>> > --
>>>>> > Sent from the Delta quadrant using Borg technology!
>>>>> >
>>>>> > Nux!
>>>>> > www.nux.ro
>>>>> >
>>>>> > ----- Original Message -----
>>>>> >> From: "Nux!" <n...@li.nux.ro>
>>>>> >> To: dev@cloudstack.apache.org
>>>>> >> Sent: Monday, 2 March, 2015 17:41:39
>>>>> >> Subject: Re: [VOTE] Apache CloudStack 4.5.0 RC4
>>>>> >
>>>>> >> Hi,
>>>>> >>
>>>>> >> Testing time!
>>>>> >>
>>>>> >> EL6 OSS rpms here:
>>>>> >> http://tmp.nux.ro/acs450/
>>>>> >>
>>>>> >> --
>>>>> >> Sent from the Delta quadrant using Borg technology!
>>>>> >>
>>>>> >> Nux!
>>>>> >> www.nux.ro
>>>>> >>
>>>>> >> ----- Original Message -----
>>>>> >>> From: "David Nalley" <da...@gnsa.us>
>>>>> >>> To: dev@cloudstack.apache.org
>>>>> >>> Sent: Monday, 2 March, 2015 16:49:20
>>>>> >>> Subject: [VOTE] Apache CloudStack 4.5.0 RC4
>>>>> >>
>>>>> >>> Hi All,
>>>>> >>>
>>>>> >>> I've created yet another 4.5.0 release candidate, with the
>>>>> >>> following artifacts up for a vote:
>>>>> >>>
>>>>> >>> Git Branch and Commit SH:
>>>>> >>>
>>>>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;
>>>>> h=refs/heads/4.5-RC20150302T1625
>>>>> >>> Commit: c066f0455fa126a2b41cccefa25b56421a445d99
>>>>> >>>
>>>>> >>> Source release (checksums and signatures are available at the
>>>>> >>> same
>>>>> >>> location):
>>>>> >>> https://dist.apache.org/repos/dist/dev/cloudstack/4.5.0-rc4/
>>>>> >>>
>>>>> >>> PGP release keys (signed using 0x6fe50f1c):
>>>>> >>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>>>>> >>>
>>>>> >>> Vote will be open for at least 72 hours.
>>>>> >>>
>>>>> >>> For sanity in tallying the vote, can PMC members please be sure
>>>>> >>> to indicate "(binding)" with their vote?
>>>>> >>>
>>>>> >>> [ ] +1  approve
>>>>> >>> [ ] +0  no opinion
>>>>> >> > [ ] -1  disapprove (and reason why)
>>>>>
>> Find out more about ShapeBlue and our range of CloudStack related services
>>
>> IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//>
>> CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/>
>> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/>
>> CloudStack Software
>> Engineering<http://shapeblue.com/cloudstack-software-engineering/>
>> CloudStack Infrastructure
>> Support<http://shapeblue.com/cloudstack-infrastructure-support/>
>> CloudStack Bootcamp Training 
>> Courses<http://shapeblue.com/cloudstack-training/>
>>
>> This email and any attachments to it may be confidential and are intended 
>> solely
>> for the use of the individual to whom it is addressed. Any views or opinions
>> expressed are solely those of the author and do not necessarily represent 
>> those
>> of Shape Blue Ltd or related companies. If you are not the intended recipient
>> of this email, you must neither take any action based upon its contents, nor
>> copy or show it to anyone. Please contact the sender if you believe you have
>> received this email in error. Shape Blue Ltd is a company incorporated in
>> England & Wales. ShapeBlue Services India LLP is a company incorporated in
>> India and is operated under license from Shape Blue Ltd. Shape Blue Brasil
>> Consultoria Ltda is a company incorporated in Brasil and is operated under
>> license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by
>> The Republic of South Africa and is traded under license from Shape Blue Ltd.
> > ShapeBlue is a registered trademark.

Reply via email to