Re: Upgrading from 4.9.3 to 4.11

2018-11-05 Thread Sergey Levitskiy 
It seems your screenshot was lost. Can you re-send/save it somewhere and we 
will take a look?

From: "McClune, James" 
Reply-To: "users@cloudstack.apache.org" 
Date: Monday, November 5, 2018 at 7:34 AM
To: "users@cloudstack.apache.org" 
Cc: "Adams, Christopher" 
Subject: Re: Upgrading from 4.9.3 to 4.11

Hi Sergey,

Thank you for the feedback! :)

I managed to update the schema to 4.10. I'm trying to get to 4.11. However, I'm 
running into these errors now:

2018-11-05 10:23:19,896 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:) Is 
Data Base High Availiability enabled? Ans : false
2018-11-05 10:23:20,233 DEBUG [c.c.u.d.DriverLoader] (main:null) (logid:) 
Successfully loaded DB driver com.mysql.jdbc.Driver
2018-11-05 10:23:20,239 DEBUG [c.c.u.d.DriverLoader] (main:null) (logid:) DB 
driver com.mysql.jdbc.Driver was already loaded.
2018-11-05 10:23:20,240 DEBUG [c.c.u.d.DriverLoader] (main:null) (logid:) DB 
driver com.mysql.jdbc.Driver was already loaded.
2018-11-05 10:23:20,567 DEBUG [c.c.u.d.ConnectionConcierge] (main:null) 
(logid:) Registering a database connection for LockMaster1
2018-11-05 10:23:20,567 INFO  [c.c.u.d.Merovingian2] (main:null) (logid:) 
Cleaning up locks for 90520739700260
2018-11-05 10:23:20,580 INFO  [c.c.u.d.Merovingian2] (main:null) (logid:) 
Released 0 locks for 90520739700260
2018-11-05 10:23:20,951 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] 
(main:null) (logid:) Running system integrity checker 
com.cloud.upgrade.DatabaseUpgradeChecker@1e6b9a95
2018-11-05 10:23:20,952 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) 
(logid:) Grabbing lock to check for database upgrade.
2018-11-05 10:23:21,042 DEBUG [c.c.u.d.VersionDaoImpl] (main:null) (logid:) 
Checking to see if the database is at a version before it was the version table 
is created
2018-11-05 10:23:21,078 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) 
(logid:) DB version = 4.10.0.0 Code Version = 4.11.0.0
2018-11-05 10:23:21,079 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) 
(logid:) Database upgrade must be performed from 4.10.0.0 to 4.11.0.0
2018-11-05 10:23:21,081 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) 
(logid:) Running upgrade Upgrade41000to41100 to upgrade from 4.10.0.0-4.11.0.0 
to 4.11.0.0
2018-11-05 10:23:21,086 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
Licensed to the Apache Software Foundation (ASF) under one
2018-11-05 10:23:21,086 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- or 
more contributor license agreements.  See the NOTICE file
2018-11-05 10:23:21,086 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
distributed with this work for additional information
2018-11-05 10:23:21,086 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
regarding copyright ownership.  The ASF licenses this file
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- to 
you under the Apache License, Version 2.0 (the
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
"License"); you may not use this file except in compliance
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
with the License.  You may obtain a copy of the License at
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --   
http://www.apache.org/licenses/LICENSE-2.0
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
Unless required by applicable law or agreed to in writing,
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
software distributed under the License is distributed on an
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
KIND, either express or implied.  See the License for the
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
specific language governing permissions and limitations
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
under the License.
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --;
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
Schema upgrade from 4.10.0.0 to 4.11.0.0
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --;
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) -- 
Add For VPC flag
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) ALTER 
TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL DEFAULT 0
2018-11-05 10:23:21,092 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:) Error 
executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT 
NULL D

Re: Upgrading from 4.9.3 to 4.11

2018-11-05 Thread McClune, James 
Hi Sergey,

Thank you for the feedback! :)

I managed to update the schema to 4.10. I'm trying to get to 4.11. However,
I'm running into these errors now:

2018-11-05 10:23:19,896 INFO  [c.c.u.d.T.Transaction] (main:null) (logid:)
Is Data Base High Availiability enabled? Ans : false
2018-11-05 10:23:20,233 DEBUG [c.c.u.d.DriverLoader] (main:null) (logid:)
Successfully loaded DB driver com.mysql.jdbc.Driver
2018-11-05 10:23:20,239 DEBUG [c.c.u.d.DriverLoader] (main:null) (logid:)
DB driver com.mysql.jdbc.Driver was already loaded.
2018-11-05 10:23:20,240 DEBUG [c.c.u.d.DriverLoader] (main:null) (logid:)
DB driver com.mysql.jdbc.Driver was already loaded.
2018-11-05 10:23:20,567 DEBUG [c.c.u.d.ConnectionConcierge] (main:null)
(logid:) Registering a database connection for LockMaster1
2018-11-05 10:23:20,567 INFO  [c.c.u.d.Merovingian2] (main:null) (logid:)
Cleaning up locks for 90520739700260
2018-11-05 10:23:20,580 INFO  [c.c.u.d.Merovingian2] (main:null) (logid:)
Released 0 locks for 90520739700260
2018-11-05 10:23:20,951 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle]
(main:null) (logid:) Running system integrity checker
com.cloud.upgrade.DatabaseUpgradeChecker@1e6b9a95
2018-11-05 10:23:20,952 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null)
(logid:) Grabbing lock to check for database upgrade.
2018-11-05 10:23:21,042 DEBUG [c.c.u.d.VersionDaoImpl] (main:null) (logid:)
Checking to see if the database is at a version before it was the version
table is created
2018-11-05 10:23:21,078 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null)
(logid:) DB version = 4.10.0.0 Code Version = 4.11.0.0
2018-11-05 10:23:21,079 INFO  [c.c.u.DatabaseUpgradeChecker] (main:null)
(logid:) Database upgrade must be performed from 4.10.0.0 to 4.11.0.0
2018-11-05 10:23:21,081 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null)
(logid:) Running upgrade Upgrade41000to41100 to upgrade from
4.10.0.0-4.11.0.0 to 4.11.0.0
2018-11-05 10:23:21,086 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- Licensed to the Apache Software Foundation (ASF) under one
2018-11-05 10:23:21,086 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- or more contributor license agreements.  See the NOTICE file
2018-11-05 10:23:21,086 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- distributed with this work for additional information
2018-11-05 10:23:21,086 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- regarding copyright ownership.  The ASF licenses this file
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- to you under the Apache License, Version 2.0 (the
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- "License"); you may not use this file except in compliance
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- with the License.  You may obtain a copy of the License at
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
--   http://www.apache.org/licenses/LICENSE-2.0
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:) --
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- Unless required by applicable law or agreed to in writing,
2018-11-05 10:23:21,087 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- software distributed under the License is distributed on an
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- KIND, either express or implied.  See the License for the
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- specific language governing permissions and limitations
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- under the License.
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
--;
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- Schema upgrade from 4.10.0.0 to 4.11.0.0
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
--;
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
-- Add For VPC flag
2018-11-05 10:23:21,088 DEBUG [c.c.u.d.ScriptRunner] (main:null) (logid:)
ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc INT(1) NOT NULL
DEFAULT 0
2018-11-05 10:23:21,092 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
Error executing: ALTER TABLE cloud.network_offerings ADD COLUMN for_vpc
INT(1) NOT NULL DEFAULT 0
2018-11-05 10:23:21,093 ERROR [c.c.u.d.ScriptRunner] (main:null) (logid:)
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column
name 'for_vpc'
2018-11-05 10:23:21,094 ERROR [c.c.u.DatabaseUpgradeChecker] (main:null)
(logid:) Unable to execute upgrade script
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Duplicate column
name 'for_vpc'
at

Re: Upgrading from 4.9.3 to 4.11

2018-11-03 Thread Sergey Levitskiy 
Basically version of Cloudstack you are running has already some pieces of the 
code that is part of the upgrade from 4.9.3 to 4.10. This could have happened 
if you deployed a fix on the top of 4.9.3 or if a PR was backported to 4.9.3 
codebase after you install. You still can perform successful upgrade with some 
manual effort:
1. Make a copy of you CS DB.
2. Obtain the file schema-4930to41000.sql. 
https://github.com/apache/cloudstack/blob/1d05fead49f5c856257a741b07122f5633d2e359/engine/schema/src/main/resources/META-INF/db/schema-4930to41000.sql
3. Execute it on the copy of your DB. It will fail initially with the same 
error as in yourACS log
Error executing: ALTER TABLE `cloud`.`domain_router` ADD COLUMN 
update_state varchar(64) DEFAULT NULL
 2018-11-02 08:28:48,787 ERROR [c.c.u.d.ScriptRunner] 
(main:null) (logid:)
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: 
Duplicate column name 'update_state'
4. Comment line 22 in SQL file. Restore your DB copy
5. Continue steps 2-4 until you have successful processing of SQL file against 
a copy of your DB
(6 optional) Likely this will be enough to unblock your upgrade but if you want 
to ensure throughout upgrade you might need to repeat the same with 4.11 and 
4.11.1 upgrade files. You will need to do a sequence 4.9.3->4.10->4.11->4.11.1 
in each iteration.

https://github.com/apache/cloudstack/blob/1d05fead49f5c856257a741b07122f5633d2e359/engine/schema/src/main/resources/META-INF/db/schema-41000to41100.sql

https://github.com/apache/cloudstack/blob/1d05fead49f5c856257a741b07122f5633d2e359/engine/schema/src/main/resources/META-INF/db/schema-41100to41110.sql

7. Now you have adjusted DB upgrade file(s). Next step as to re-try your 
upgrade. After you update packages on the first management server but before 
your re-start the cloudstack-managment service you need to replace DB upgrade 
file in /usr/share/cloudstack-management/setup/db

Good luck.

Thanks,
Sergey



On 11/2/18, 9:19 AM, "McClune, James"  wrote:

Hello CloudStack Community,

I was wondering if you could help me a little further. I referenced the
documentation Rohit sent:


http://docs.cloudstack.apache.org/en/4.11.1.0/upgrading/upgrade/upgrade-4.9.html

I backed up my cloud database and followed the instructions verbatim. My
CloudStack management server is running on Ubuntu 14.04. When I upgrade my
packages to 4.11, the management doesn't start correctly (/client 404
error). I was getting errors along the lines of "Cannot connect to
database". I checked my db.properties file and made sure the
cluster.node.ip was set correctly, as well as database authentication (e.g.
MySQL username/password). I ran the Java command to encrypt my database
password, as described here:


http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.11/management.html#changing-the-database-password

I added the password to db.properties, hoping that my authentication was
somehow screwed up. I still got the errors. I didn't catch those errors,
but I'll retry and send them to you.

I also tried doing a manual upgrade and re-importing the database schema.
However, the 4.9.3 schema is different from 4.11 (as expected), so I
started to get errors:

root@cloudstack:~# tail -f
/var/log/cloudstack/management/management-server.log
2018-11-01 21:04:50,909 INFO  [o.e.j.s.h.ContextHandler] (main:null)
(logid:) Started o.e.j.s.h.MovedContextHandler@5cdd8682{/,null,AVAILABLE}
2018-11-02 08:28:23,152 INFO  [o.a.c.ServerDaemon] (main:null) (logid:)
Server configuration file found:
/etc/cloudstack/management/server.properties
2018-11-02 08:28:23,160 INFO  [o.a.c.ServerDaemon] (main:null) (logid:)
Initializing server daemon on :::8080, with https.enabled=false,
https.port=8443, context.path=/client
2018-11-02 08:28:23,172 INFO  [o.e.j.u.log] (main:null) (logid:) Logging
initialized @853ms to org.eclipse.jetty.util.log.Slf4jLog
2018-11-02 08:28:23,406 INFO  [o.e.j.s.Server] (main:null) (logid:)
jetty-9.4.z-SNAPSHOT, build timestamp: 2017-11-21T16:27:37-05:00, git hash:
82b8fb23f757335bb3329d540ce37a2a2615f0a8
2018-11-02 08:28:23,454 INFO  [o.e.j.s.AbstractNCSARequestLog] (main:null)
(logid:) Opened /var/log/cloudstack/management/access.log
2018-11-02 08:28:23,586 INFO  [o.e.j.w.StandardDescriptorProcessor]
(main:null) (logid:) NO JSP Support for /client, did not find
org.eclipse.jetty.jsp.JettyJspServlet
2018-11-02 08:28:23,619 INFO  [o.e.j.s.session] (main:null) (logid:)
DefaultSessionIdManager workerName=node0
2018-11-02 08:28:23,619 INFO  [o.e.j.s.session] (main:null) (logid:) No
SessionScavenger set, using defaults
2018-11-02 08:28:23,621 INFO  [o.e.j.s.session] (main:null) (logid:)
Scavenging every 66ms
2018-11-02 08:28:45,916

Upgrading from 4.9.3 to 4.11

2018-11-02 Thread McClune, James 
Hello CloudStack Community,

I was wondering if you could help me a little further. I referenced the
documentation Rohit sent:

http://docs.cloudstack.apache.org/en/4.11.1.0/upgrading/upgrade/upgrade-4.9.html

I backed up my cloud database and followed the instructions verbatim. My
CloudStack management server is running on Ubuntu 14.04. When I upgrade my
packages to 4.11, the management doesn't start correctly (/client 404
error). I was getting errors along the lines of "Cannot connect to
database". I checked my db.properties file and made sure the
cluster.node.ip was set correctly, as well as database authentication (e.g.
MySQL username/password). I ran the Java command to encrypt my database
password, as described here:

http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.11/management.html#changing-the-database-password

I added the password to db.properties, hoping that my authentication was
somehow screwed up. I still got the errors. I didn't catch those errors,
but I'll retry and send them to you.

I also tried doing a manual upgrade and re-importing the database schema.
However, the 4.9.3 schema is different from 4.11 (as expected), so I
started to get errors:

root@cloudstack:~# tail -f
/var/log/cloudstack/management/management-server.log
2018-11-01 21:04:50,909 INFO  [o.e.j.s.h.ContextHandler] (main:null)
(logid:) Started o.e.j.s.h.MovedContextHandler@5cdd8682{/,null,AVAILABLE}
2018-11-02 08:28:23,152 INFO  [o.a.c.ServerDaemon] (main:null) (logid:)
Server configuration file found:
/etc/cloudstack/management/server.properties
2018-11-02 08:28:23,160 INFO  [o.a.c.ServerDaemon] (main:null) (logid:)
Initializing server daemon on :::8080, with https.enabled=false,
https.port=8443, context.path=/client
2018-11-02 08:28:23,172 INFO  [o.e.j.u.log] (main:null) (logid:) Logging
initialized @853ms to org.eclipse.jetty.util.log.Slf4jLog
2018-11-02 08:28:23,406 INFO  [o.e.j.s.Server] (main:null) (logid:)
jetty-9.4.z-SNAPSHOT, build timestamp: 2017-11-21T16:27:37-05:00, git hash:
82b8fb23f757335bb3329d540ce37a2a2615f0a8
2018-11-02 08:28:23,454 INFO  [o.e.j.s.AbstractNCSARequestLog] (main:null)
(logid:) Opened /var/log/cloudstack/management/access.log
2018-11-02 08:28:23,586 INFO  [o.e.j.w.StandardDescriptorProcessor]
(main:null) (logid:) NO JSP Support for /client, did not find
org.eclipse.jetty.jsp.JettyJspServlet
2018-11-02 08:28:23,619 INFO  [o.e.j.s.session] (main:null) (logid:)
DefaultSessionIdManager workerName=node0
2018-11-02 08:28:23,619 INFO  [o.e.j.s.session] (main:null) (logid:) No
SessionScavenger set, using defaults
2018-11-02 08:28:23,621 INFO  [o.e.j.s.session] (main:null) (logid:)
Scavenging every 66ms
2018-11-02 08:28:45,916 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Loading module context [bootstrap] from URL
[jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.11.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context.xml]
2018-11-02 08:28:45,917 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Loading module context [bootstrap] from URL
[jar:file:/usr/share/cloudstack-management/lib/cloudstack-4.11.0.0.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]
2018-11-02 08:28:46,132 DEBUG [c.c.u.c.EncryptionSecretKeyChecker]
(main:null) (logid:) Encryption Type: file
2018-11-02 08:28:46,186 INFO  [c.c.u.LogUtils] (main:null) (logid:) log4j
configuration found at /etc/cloudstack/management/log4j-cloud.xml
2018-11-02 08:28:46,233 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Loaded module context [bootstrap] in 317 ms
2018-11-02 08:28:46,236 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy: bootstrap
2018-11-02 08:28:46,236 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy:   system
2018-11-02 08:28:46,237 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy: core
2018-11-02 08:28:46,237 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy:   allocator
2018-11-02 08:28:46,237 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy: host-allocator-random
2018-11-02 08:28:46,237 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy: planner
2018-11-02 08:28:46,238 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy:   api-planner
2018-11-02 08:28:46,238 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy:   baremetal-planner
2018-11-02 08:28:46,238 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy:   explicit-dedication
2018-11-02 08:28:46,238 INFO  [o.a.c.s.m.m.i.DefaultModuleDefinitionSet]
(main:null) (logid:) Module Hierarchy:   host-anti-affinity
2018-11-02 08:28:46,239 INFO

Re: Upgrading from 4.9.3 to 4.11

2018-10-31 Thread Rohit Yadav 
Hi James,


Please use the following link for upgrading from your 4.9 installation to the 
bugfix minor 4.11 release - 4.11.1.0:

http://docs.cloudstack.apache.org/en/4.11.1.0/upgrading/upgrade/upgrade-4.9.html


The L2 feature is currently only available with the advanced zone, you'll need 
to set up a separate advanced zone with some new KVM hosts to use that feature.


- Rohit

<https://cloudstack.apache.org>




From: McClune, James 
Sent: Wednesday, October 31, 2018 10:33:41 PM
To: users@cloudstack.apache.org
Cc: Adams, Christopher
Subject: Upgrading from 4.9.3 to 4.11

Hello CloudStack Community,

I work for a school district in Ohio and we've been running ACS 4.9.3 for
over a year now. Great piece of software! We're using Ceph (Luminous) for
our storage backend and KVM/libvirt for virtualization.

We're starting to expand our private cloud. We'd like to rely on external
systems for IP services (e.g. DHCP, DNS, routing, etc.). Right now, we're
running a basic network zone (with ACS managing IP services). I'm building
a roadmap for upgrading to ACS 4.11. I'm looking to implement the L2
functionality in 4.11, as described here:

https://www.shapeblue.com/layer-2-networks-in-cloudstack/

I was wondering if anyone has advice on upgrading to 4.11 from 4.9.3 (i.e.
important things to watch for, problems encountered, etc.). I'm referencing
the documentation here:

http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html

I appreciate all input! :)

Thanks,

--

James McClune

Technical Support Specialist

Norwalk City Schools

Phone: 419-660-6590

mcclu...@norwalktruckers.net

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue

Re: Upgrading from 4.9.3 to 4.11

2018-10-31 Thread ilya musayev 
You’d have to put a separate Advanced Zone to use L2 Networking. 

What would be delegating DHCP and managing DNS? 

If you can keep the DHCP+Metadata with cloudstack Router VM (it will only do 
DHCP and Metadata and no routing) - you can use everything else from upstream 
provider. This is how most Advanced Zones with VLAN isolation deployed and we 
have many of these.

You can probably manage to abstract DHCP as well but integrating with a 
provider/plugin.. GloboDNS guys wrote some sort of integration like it - 
sometime ago.

Regards,
ilya

> On Oct 31, 2018, at 10:03 AM, McClune, James  
> wrote:
> 
> Hello CloudStack Community,
> 
> I work for a school district in Ohio and we've been running ACS 4.9.3 for
> over a year now. Great piece of software! We're using Ceph (Luminous) for
> our storage backend and KVM/libvirt for virtualization.
> 
> We're starting to expand our private cloud. We'd like to rely on external
> systems for IP services (e.g. DHCP, DNS, routing, etc.). Right now, we're
> running a basic network zone (with ACS managing IP services). I'm building
> a roadmap for upgrading to ACS 4.11. I'm looking to implement the L2
> functionality in 4.11, as described here:
> 
> https://www.shapeblue.com/layer-2-networks-in-cloudstack/
> 
> I was wondering if anyone has advice on upgrading to 4.11 from 4.9.3 (i.e.
> important things to watch for, problems encountered, etc.). I'm referencing
> the documentation here:
> 
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
> 
> I appreciate all input! :)
> 
> Thanks,
> 
> --
> 
> James McClune
> 
> Technical Support Specialist
> 
> Norwalk City Schools
> 
> Phone: 419-660-6590
> 
> mcclu...@norwalktruckers.net

Re: Upgrading from 4.9.3 to 4.11

2018-10-31 Thread Ivan Kudryavtsev 
James, AFAIK L2 Networks function is not compatible with basic zones, so
without moving to advanced zone it's impossible to use this function in CS,
so If you don't have the problems with 4.9.3 it's better to stay with 4.9.3.

Best wishes, Ivan

ср, 31 окт. 2018 г. в 13:04, McClune, James :

> Hello CloudStack Community,
>
> I work for a school district in Ohio and we've been running ACS 4.9.3 for
> over a year now. Great piece of software! We're using Ceph (Luminous) for
> our storage backend and KVM/libvirt for virtualization.
>
> We're starting to expand our private cloud. We'd like to rely on external
> systems for IP services (e.g. DHCP, DNS, routing, etc.). Right now, we're
> running a basic network zone (with ACS managing IP services). I'm building
> a roadmap for upgrading to ACS 4.11. I'm looking to implement the L2
> functionality in 4.11, as described here:
>
> https://www.shapeblue.com/layer-2-networks-in-cloudstack/
>
> I was wondering if anyone has advice on upgrading to 4.11 from 4.9.3 (i.e.
> important things to watch for, problems encountered, etc.). I'm referencing
> the documentation here:
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html
>
> I appreciate all input! :)
>
> Thanks,
>
> --
>
> James McClune
>
> Technical Support Specialist
>
> Norwalk City Schools
>
> Phone: 419-660-6590
>
> mcclu...@norwalktruckers.net
>


-- 
With best regards, Ivan Kudryavtsev
Bitworks LLC
Cell RU: +7-923-414-1515
Cell USA: +1-201-257-1512
WWW: http://bitworks.software/ <http://bw-sw.com/>

Upgrading from 4.9.3 to 4.11

2018-10-31 Thread McClune, James 
Hello CloudStack Community,

I work for a school district in Ohio and we've been running ACS 4.9.3 for
over a year now. Great piece of software! We're using Ceph (Luminous) for
our storage backend and KVM/libvirt for virtualization.

We're starting to expand our private cloud. We'd like to rely on external
systems for IP services (e.g. DHCP, DNS, routing, etc.). Right now, we're
running a basic network zone (with ACS managing IP services). I'm building
a roadmap for upgrading to ACS 4.11. I'm looking to implement the L2
functionality in 4.11, as described here:

https://www.shapeblue.com/layer-2-networks-in-cloudstack/

I was wondering if anyone has advice on upgrading to 4.11 from 4.9.3 (i.e.
important things to watch for, problems encountered, etc.). I'm referencing
the documentation here:

http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11.0.0/upgrade/upgrade-4.9.html

I appreciate all input! :)

Thanks,

--

James McClune

Technical Support Specialist

Norwalk City Schools

Phone: 419-660-6590

mcclu...@norwalktruckers.net