Re: GUI Issue

[Boris Stoyanov]

I’ve just checked and it does not work with me as well. Doesn’t look browser 
related, tried it on both chrome and FF and still not working. Let me log an 
issue about it. 

Bobby.


boris.stoya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

> On 11 Jul 2018, at 22:28, Tutkowski, Mike  wrote:
> 
> Hi,
> 
> Has anyone else noticed that you can no longer use the Quickview column to 
> manipulate (i.e. delete, in this case) Disk Offerings in the GUI in master? 
> The Quickview menu doesn’t show up. It works fine for Compute Offerings 
> still, though.
> 
> Thanks,
> Mike

GUI Issue

[Tutkowski, Mike]

Hi,

Has anyone else noticed that you can no longer use the Quickview column to 
manipulate (i.e. delete, in this case) Disk Offerings in the GUI in master? The 
Quickview menu doesn’t show up. It works fine for Compute Offerings still, 
though.

Thanks,
Mike

Re: [Proposal] new API for recover routers

[Rene Moser]

Hi Dag

On 07/11/2018 12:08 PM, Dag Sonstebo wrote:
> Hi Rene,
> 
> So if you have upgraded 4.5 to 4.11 (or any version upgrade where new system 
> VM templates are in play) then your 4.5 VRs are by definition destroyed and 
> you are running with 4.11 VRs. As a result there is nothing to recover – the 
> rollback mechanism in this case is to roll back DB, destroy all 4.11 VRs (and 
> anything else unknown to the original DB) – then start up the 4.5 management 
> servers. At this point CloudStack management will either automatically build 
> “new” 4.5 VRs – or worst case you do a network restart which recreates the VR.

Yes we know the procedure of the downgrade. The nice thing of the
upgrade is that the VR names stay as is and we thought it would be nice
if this would also be possible while "downgrading" or more precisely,
state="your VR are not in a version the running ACS supports --> recover
them"

The thing is with "destroyed VR" hey are not coming back automatically,
do they? They are only be recreated on a e.g. network restart or an api
call related to a VR (user VM stop/start, etc.) right?

Regards
René

[QUESTION] vmware disk MO use in cloudstack

[Daan Hoogland]

Fellow devs,

I am trying for some migration code in the vmware resource and noticed that
the virtualDiskManagerMO is implemented but never used. For instance ther
is an extendVirtualDisk implemented but the resize method uses a worker vm
to attach the disk an resize it there.
Does anyone know if there is a good reason not to use the
virtualDiskManagerMO?

​tnx​,

-- 
Daan

RE: Next CloudStack EU user group date

[Steve Roles]

Hi Swen and all,



Great to see so much planned activity! Wanted to let you know that the London 
CloudStack European User Group Meetup on Thursday, September 13 is confirmed 
and will be going ahead.



If you also want to hold an event in October that's fantastic. As you say - 
it's after ApacheCon and attendees can talk and share information.



Steve Roles



steve.ro...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-Original Message-
From: Swen - swen.io 
Sent: 09 July 2018 22:15
To: us...@cloudstack.apache.org
Cc: 'dev' 
Subject: AW: Next CloudStack EU user group date



Hi all,



so schedule would look like this:



13.09.2018 CloudStack European User Group (London, UK) OPTION 1

24.09.2018 - 28.09.2018 ApacheCon (Montreal, CA)

18.10.2018 CloudStack European User Group (Leipzig, DE) OPTION 2

22.10.2018 - 24.10.2018 Open Source Summit (Edinburgh, UK)



Personally I prefer the October date for the CloudStack European User Group 
Meetup because it is after ApacheCon and visitors can talk and share 
information with others who could not attend.



cu Swen



-Ursprüngliche Nachricht-

Von: Rafael Weingärtner [mailto:rafaelweingart...@gmail.com]

Gesendet: Montag, 9. Juli 2018 21:21

An: users mailto:us...@cloudstack.apache.org>>

Cc: dev mailto:dev@cloudstack.apache.org>>

Betreff: Re: Next CloudStack EU user group date



I think October is a good alternative. Andrija mentioned the Open Source Summit 
Europe, which happens this October as well. However, if this collaboration 
takes the shape of a smaller and focused meeting, I think it can work.



On Mon, Jul 9, 2018 at 4:15 PM, Sven Vogel 
mailto:s.vo...@ewerk.com>> wrote:



> Hi Rafael,

>

> Yes that’s what I thought in October?

>

> What do you think?

>

> Von meinem iPhone gesendet

>

>

> __

>

> Sven Vogel

> Cloud Solutions Architect

>

> EWERK RZ GmbH

> Brühl 24, D-04109 Leipzig

> P +49 341 42649 - 11

> F +49 341 42649 - 18

> s.vo...@ewerk.com

> www.ewerk.com

>

> Geschäftsführer:

> Dr. Erik Wende, Hendrik Schubert, Frank Richter, Gerhard Hoyer

> Registergericht: Leipzig HRB 17023

>

> Zertifiziert nach:

> ISO/IEC 27001:2013

> DIN EN ISO 9001:2015

> DIN ISO/IEC 2-1:2011

>

> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

>

> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

>

> Disclaimer Privacy:

> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien)

> ist vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht

> der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung,

> Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte

> informieren Sie in diesem Fall unverzüglich den Absender und löschen

> Sie die E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System.

> Vielen Dank.

>

> The contents of this e-mail (including any attachments) are

> confidential and may be legally privileged. If you are not the

> intended recipient of this e-mail, any disclosure, copying,

> distribution or use of its contents is strictly prohibited, and you

> should please notify the sender immediately and then delete it (including any 
> attachments) from your system. Thank you.

> > Am 09.07.2018 um 15:04 schrieb Rafael Weingärtner <

> rafaelweingart...@gmail.com>:

> >

> > Do not forget that we have CCC/ApacheCon in September 22-28.

> >

> >> On Mon, Jul 9, 2018 at 10:01 AM, Sven Vogel 
> >> mailto:s.vo...@ewerk.com>> wrote:

> >>

> >> Hi Ivan,

> >>

> >>

> >>

> >> Early September or October?  What do you think?

> >>

> >>

> >>

> >> We thought on the 18.10. Is that also possible?

> >>

> >>

> >>

> >> Thanks

> >>

> >>

> >>

> >> Sven

> >>

> >>

> >>

> >>

> >> __

> >>

> >> Sven Vogel

> >> Cloud Solutions Architect

> >>

> >> EWERK RZ GmbH

> >> Brühl 24, D-04109 Leipzig

> >> P +49 341 42649 - 11

> >> F +49 341 42649 - 18

> >> s.vo...@ewerk.com

> >> www.ewerk.com

> >>

> >> Geschäftsführer:

> >> Dr. Erik Wende, Hendrik Schubert, Frank Richter, Gerhard Hoyer

> >> Registergericht: Leipzig HRB 17023

> >>

> >> Zertifiziert nach:

> >> ISO/IEC 27001:2013

> >> DIN EN ISO 9001:2015

> >> DIN ISO/IEC 2-1:2011

> >>

> >> EWERK-Blog | LinkedIn | Xing | Twitter | Facebook

> >>

> >> Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

> >>

> >> Disclaimer Privacy:

> >> Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter

> >> Dateien)

> ist

> >> vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht

> >> der bestimmungsgemäße Empfänger sein, ist Ihnen jegliche

> >> Offenlegung, Vervielfältigung, Weitergabe oder Nutzung des Inhalts

> >> untersagt. Bitte informieren Sie in diesem Fall unverzüglich den

> >> Absender und löschen Sie die E-Mail (einschließlich 

Re: Cloudstack Collab Canada anyone?

[Ron Wheeler]

1) Work on the website and docs to make Cloudstack look more attractive 
for people looking for a cloud orchestration solution.

- clear description of what it does
- clearly identify target environments - company datacentres, cloud 
service providers, software development teams, etc.
- clear identification of benefits for each target as opposed to other 
solutions

- add customer testimonials from each of the target markets.

2) cleanup roadmap, remove wrong and contradictory information

3) use social media to direct people to the new information.


The team has done a great job in getting a strong presence in the 
presentations


4) put out a regular stream of messaging about each of the presentations 
in social media.
There are some local Montreal groups on social media. I will try to add 
to the list.

- https://twitter.com/technomontreal?lang=en
- https://www.linkedin.com/company/technomontr%C3%A9al/?originalSubdomain=ca
- https://www.meetup.com/cities/ca/qc/montr%C3%A9al/tech/

Perhaps we should develop a list of "important" social media venues and 
regularly share important news on them.



Ron



On 11/07/2018 5:52 AM, Giles Sirett wrote:

All good to hear - looking forward to seeing you all

Whilst we're on this subject, I thought I would chime in with this:

This will be the second year that we've co-located Cloudstack Collaboration 
Conference with Apachecon. Last year (Miami) was really successful: great 
agenda, great talks, really well organised. However, our attendance was down 
compared with all previous CloudStack Collaboration Conferences.

IMO, this was down to the fact that, previously, we had always promoted CCC from within 
the community as it was "our" event. However, last year, I think we all sat 
back a little and expected Apachecon folks to do that.

A lot of work has gone in to putting a great agenda together again 
(http://ca.cloudstackcollab.org/#schedule)


I see  that many people on this list will already be coming (or considering 
coming)  either specifically for Cloudstack collab or to attend the broader 
apachecon talks,  but it would be really great if we can get the attendance up 
from last year.

So, if everybody could help us a little, it would be very much apprecited

Some specific call outs:
1. please share on social media (look for @cloudstack @ApacheCon). Share your 
talk, share others talk, share the conference generally
2. If you're in this community, please make every effort to try and come. These 
conferences really are great for ideas, sharing problems, learning, working 
together, etc
3. Bring others: if you're coming, bring a colleague, bring a customer, bring a 
partner (Montreal is a great City)

Any other ideas?


Kind regards
Giles

giles.sir...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
   
  



-Original Message-
From: Simon Weller 
Sent: 10 July 2018 15:03
To: us...@cloudstack.apache.org
Subject: Re: Cloudstack Collab Canada anyone?

ENA plans to be there as well.





From: David Merrill 
Sent: Tuesday, July 10, 2018 8:17 AM
To: us...@cloudstack.apache.org
Subject: Re: Cloudstack Collab Canada anyone?

And one from Portland, Maine...

David Merrill
Senior Systems Engineer,
Managed and Private/Hybrid Cloud Services OTELCO
92 Oak Street, Portland ME 04101
office 207.772.5678
www.otelco.com /business/managed-services

- Original Message -
From: "Andrija Panic" 
To: "users" 
Sent: Tuesday, July 10, 2018 7:00:21 AM
Subject: Re: Cloudstack Collab Canada anyone?

To answer my own question :) from HIAG it will be 3 / 4 of us.

On Tue, Jul 10, 2018, 10:42 Jochim, Ingo  wrote:


Hi all,

from itelligence we will be four guys coming to Montreal.

See you soon.
Regards,
Ingo

-Original Message-
From: Boris Stoyanov [mailto:boris.stoya...@shapeblue.com]
Sent: Dienstag, 10. Juli 2018 10:08
To: users 
Subject: Re: Cloudstack Collab Canada anyone?

Hvala Andrija,

As usual ~all of Shapeblue Egineering team will be present, and
definitely we'll organize something, looking forward!

Boris Stoyanov


boris.stoya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK @shapeblue




On 10 Jul 2018, at 10:29, Andrija Panic  wrote:

Hi all,

I was wondering who would be going to Apache CloudStack Collab conference
of 2018 on September 24-26th, Montreal, Canada?

I know it's still early, but if you know, we could (a bit later i.e.
beginning of September) organise some beer sessions or so, after the
official presentation hours are done, catch up, team spirit buildup and
such...

Cheers
Andrija




--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102

[PROPOSE] Async jobs add endtime

[Ernie Janse van Rensburg]

Hi


I have made an enhancement to the Async Jobs completion process.


Upon Async job completion, regardless of the status, it updates the removed 
field with the timestamp of when the job completed.


Please review the PR for more details:

https://github.com/apache/cloudstack/pull/2739

[https://avatars3.githubusercontent.com/u/30108093?s=400=4]

Async jobs add endtime by ernjvr · Pull Request #2739 · 
apache/cloudstack
github.com
Description Overview: There is currently no functional mechanism that captures 
or persists the end time of when an asynchronous job has finished. As a result, 
users are not able to do any reporting...

Thanks


Regards


Ernie Janse van Rensburg


ernie.jvrensb...@shapeblue.com


www.shapeblue.com

,
@shapeblue



ernie.jvrensb...@shapeblue.com 
www.shapeblue.com
,   
@shapeblue
  
 

Re: [Proposal] new API for recover routers

[Dag Sonstebo]

Hi Rene,

So if you have upgraded 4.5 to 4.11 (or any version upgrade where new system VM 
templates are in play) then your 4.5 VRs are by definition destroyed and you 
are running with 4.11 VRs. As a result there is nothing to recover – the 
rollback mechanism in this case is to roll back DB, destroy all 4.11 VRs (and 
anything else unknown to the original DB) – then start up the 4.5 management 
servers. At this point CloudStack management will either automatically build 
“new” 4.5 VRs – or worst case you do a network restart which recreates the VR.

If you haven’t upgraded the VRs – and they are still running as version 4.5 
under a 4.11 management server – then the rollback is a straight forward DB 
rollback and management restart – the original VRs will stay in place.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 11/07/2018, 10:49, "Rene Moser"  wrote:

Hi

While tested v4.11.1 in the lab and upgraded the routers, we came across
the need of "downgrade" the routers after rolled back to ACS to v4.5
(testing upgrade process).

So my proposal is to have a new api for recover the routers to the
system-vm template, AFAICS similar to

https://cloudstack.apache.org/api/apidocs-4.11/apis/recoverVirtualMachine.html
but for routers.

Any thoughts?

Regards
René




dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

[Proposal] new API for recover routers

[Rene Moser]

Hi

While tested v4.11.1 in the lab and upgraded the routers, we came across
the need of "downgrade" the routers after rolled back to ACS to v4.5
(testing upgrade process).

So my proposal is to have a new api for recover the routers to the
system-vm template, AFAICS similar to
https://cloudstack.apache.org/api/apidocs-4.11/apis/recoverVirtualMachine.html
but for routers.

Any thoughts?

Regards
René

Re: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT

[Andrei Mikhailovsky]

Hi Andrija,


>From what I recall this was not an issue for us on 4.9.x. The problem started 
>after we've upgraded. We do have a few networks that does require a static 
>nat, so it is not really an option for us.

Its a shame that such an artefact hasn't been identified during the automated / 
manual testing prior to the release and the fix hasn't been included in the 
latest point release despite having fixes for over 100 issues, some of which 
are far less serious. Not too sure what to think of it to be honest. Seems like 
one step forward, two steps backwards with the new releases (

Andrei


- Original Message -
> From: "Andrija Panic" 
> To: "dev" 
> Sent: Monday, 9 July, 2018 22:39:06
> Subject: Re: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT

> Andrei, if not mistaken I believe I saw same behavior even on 4.8 - in our
> case, what I vaguely remember was, that we configure Port Forwarding
> instead of Static NAT - it did solve our use case (for some customer), but
> maybe it's not acceptable for you...
> 
> Cheers
> 
> On Mon, 9 Jul 2018 at 18:27, Andrei Mikhailovsky 
> wrote:
> 
>> Hi Rohit,
>>
>> I would like to send you a quick update on this issue. I have recently
>> upgraded to 4.11.1.0 with the new system vm templates. The issue that I've
>> described is still present in the latest release. Hasn't it been included
>> in the latest 4.11 maintenance release? I thought that it would be as it
>> breaks the major function of the VPC.
>>
>> Cheers.
>>
>> Andrei
>>
>> - Original Message -
>> > From: "Andrei Mikhailovsky" 
>> > To: "dev" 
>> > Sent: Friday, 20 April, 2018 11:52:30
>> > Subject: Re: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT
>>
>> > Thanks
>> >
>> >
>> >
>> > - Original Message -
>> >> From: "Rohit Yadav" 
>> >> To: "dev" , "dev" > >
>> >> Sent: Friday, 20 April, 2018 10:35:55
>> >> Subject: Re: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT
>> >
>> >> Hi Andrei,
>> >>
>> >> I've fixed this recently, please see
>> >> https://github.com/apache/cloudstack/pull/2579
>> >>
>> >> As a workaround you can add routing rules manually. On the PR, there is
>> a link
>> >> to a comment that explains the issue and suggests manual workaround.
>> Let me
>> >> know if that works for you.
>> >>
>> >> Regards.
>> >>
>> >>
>> >> From: Andrei Mikhailovsky
>> >> Sent: Friday, 20 April, 2:21 PM
>> >> Subject: Upgrade from ACS 4.9.X to 4.11.0 broke VPC source NAT
>> >> To: dev
>> >>
>> >>
>> >> Hello, I have been posting to the users thread about this issue. here
>> is a quick
>> >> summary in case if people contributing to the source nat code on the
>> VPC side
>> >> would like to fix this issue. Problem summary: no connectivity between
>> virtual
>> >> machines behind two Static NAT networks. Problem case: When one virtual
>> machine
>> >> sends a packet to the external address of the another virtual machine
>> that are
>> >> handled by the same router and both are behind the Static NAT the
>> traffic does
>> >> not work. 10.1.10.100 10.1.10.1:eth2 eth3:10.1.20.1 10.1.20.100 virt1
>> router
>> >> virt2 178.248.108.77:eth1:178.248.108.113 a single packet is send from
>> virt1 to
>> >> virt2. stage1: it arrives to the router on eth2 and enters
>> "nat_PREROUTING"
>> >> IN=eth2 OUT= SRC=10.1.10.100 DST=178.248.108.113) goes through the "10
>> 1K DNAT
>> >> all -- * * 0.0.0.0/0 178.248.108.113 to:10.1.20.100 " rule and has the
>> DST
>> >> DNATED to the internal IP of the virt2 stage2: Enters the FORWARDING
>> chain and
>> >> is being DROPPED by the default policy. DROPPED:IN=eth2 OUT=eth1
>> >> SRC=10.1.10.100 DST=10.1.20.100 The reason being is that the OUT
>> interface is
>> >> not correctly changed from eth1 to eth3 during the nat_PREROUTING so
>> the packet
>> >> is not intercepted by the FORWARD rule and thus not accepted. "24 14K
>> >> ACL_INBOUND_eth3 all -- * eth3 0.0.0.0/0 10.1.20.0/24" stage3: manually
>> >> inserted rule to accept this packet for FORWARDING. the packet enters
>> the
>> >> "nat_POSTROUTING" chain IN= OUT=eth1 SRC=10.1.10.100 DST=10.1.20.100
>> and has
>> >> the SRC changed to the external IP 16 1320 SNAT all -- * eth1
>> 10.1.10.100
>> >> 0.0.0.0/0 to:178.248.108.77 and is sent to the external network on
>> eth1.
>> >> 13:37:44.834341 IP 178.248.108.77 > 10.1.20.100: ICMP echo request, id
>> 2644,
>> >> seq 2, length 64 For some reason, during the nat_PREROUTING stage the
>> DST_IP is
>> >> changed, but the OUT interface still reflects the interface associated
>> with the
>> >> old DST_IP. Here is the routing table # ip route list default via
>> 178.248.108.1
>> >> dev eth1 10.1.10.0/24 dev eth2 proto kernel scope link src 10.1.10.1
>> >> 10.1.20.0/24 dev eth3 proto kernel scope link src 10.1.20.1
>> 169.254.0.0/16 dev
>> >> eth0 proto kernel scope link src 169.254.0.5 178.248.108.0/25 dev eth1
>> proto
>> >> kernel scope link src 178.248.108.101 # ip rule list 0: from all lookup
>> local
>> >> 32761: from all fwmark 0x3 lookup 

Re: _configDao.isPremium() please help where this information comes from.

[Dingane Hlaluku]

Hi Stephan


The Noredist CloudStack build has additional dependencies that you need to 
download and install yourself. The instruction on how to get and install this 
jars is detailed under the section 'Dependencies' here: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack


After installing these jars, build using:


mvn clean install -Dnoredist -P developer,systemvm



You can also download prebuilt System VM templates for your specific hypervisor 
here: http://packages.shapeblue.com/systemvmtemplate/4.11/


These templates need to be extracted and installed in your secondary storage, 
and this can be done using this script:


scripts/storage/secondary/cloud-install-sys-tmplt


Here is an example below of how to download, extract and install system vm 
template. The NFS server is configured in the localhost.


wget 
http://packages.shapeblue.com/systemvmtemplate/4.11/systemvmtemplate-4.11.1-kvm.qcow2.bz2

./scripts/storage/secondary/cloud-install-sys-tmplt \

   -m / -f systemvmtemplate-4.11.1-kvm.qcow2.bz2

   -h kvm -o localhost -r cloud -d cloud



I hope this helps.


Regards

Dingane



From: Stephan Seitz 
Sent: Wednesday, July 11, 2018 9:44:38 AM
To: dev@cloudstack.apache.org; users
Subject: Re: _configDao.isPremium() please help where this information comes 
from.

Hey Boris!

This isn't the problem, just setting

mvn install -P deps -Dnoredist -Dnonoss; # this target doesn't work

export ACS_BUILD_OPTS="-Dnoredist -Dnonoss"; dpkg-buildpackage

I don't know what's the difference between noredist and nonoss.


Anyway if I do build the packages with noredist (which is mentioned way more 
often than nonoss in different documentations / Install.txt's),
I do not know how to include the respective *jar's getting baked into the 
systemvmtemplate. Otherwise the cloud service won't start and no further
configuration of the systemvm will take place. Say: it won't connect to the 
management.

I'm currently using tools/appliance -> build.sh systemvmtemplate, but afaik, 
these scripts doesn't honor noredist?




Am Mittwoch, den 11.07.2018, 07:03 + schrieb Boris Stoyanov:
> Hi Stephan,
>
> have you tried:
> mvn clean install -P developer,systemvm -D noredis
>
> here’s more info 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack
>
> Bobby.
>
>
> boris.stoya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>

dingane.hlal...@shapeblue.com 
www.shapeblue.com
,   
@shapeblue
  
 

> On 10 Jul 2018, at 18:19, Stephan Seitz 
> mailto:s.se...@heinlein-support.de>> wrote:
>
> Thanks for your feedback! Do you know how to build the systemvmtemplate w/ 
> noredist? I didn't find
> anything regarding that in tools/appliance, also cwiki keeps quiet about that.
>
> Thanks!
>
> Stepnan
>
> Am Dienstag, den 10.07.2018, 07:38 -0700 schrieb Frank Maximus:
> That setting is part of a property file of
> cloudstack-plugin-hypervisor-vmware.
> Most likely you are using a system build with noredist.
> In that case you also need a systemvm build that way.
>
> Kind Regards,
> Frank
>
> On Tue, Jul 10, 2018 at 12:16 PM Stephan Seitz 
> mailto:s.se...@heinlein-support.de>>
> wrote:
>
>
> Hi there,
>
> Upgrading 4.11.0 to 4.11.1 we found an interesting problem in our (well
> played) staging infrastructure.
>
> During SSVN provisioning, a somewhat "premium" configuration is detected
> (well we're using noredist since ... ever?).
> So the SSVM is configured with
>   resource=com.cloud.storage.resource.PremiumSecondaryStorageResource
> instead of
>
> resource=org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource
>
> In fact this particular setup always used (and should further use) simple
> NFS as Secondary Storage.
>
> Sorry, but I can't find the real source
> of com.cloud.configuration.dao.ConfigurationDao#isPremium() and how to set
> this to false.
>
> If anyone could shed some light?
>
>
> Thank You!
>
>
>
>
> Mit freundlichen Grüßen,
>
> Stephan Seitz
>
>
> --
> Heinlein Support GmbH
> Schwedter Str. 8/9b, 10119 Berlin
>
> https://www.heinlein-support.de
>
> Tel: 030 / 405051-44
> Fax: 030 / 405051-19
>
> Amtsgericht Berlin-Charlottenburg - HRB 93818 B
> Geschäftsführer: Peer Heinlein - Sitz: Berlin
>
>
> Mit freundlichen Grüßen,
>
> Stephan Seitz
>
>
> --
> Heinlein Support GmbH
> Schwedter Str. 8/9b, 10119 Berlin
>
> https://www.heinlein-support.de
>
> Tel: 030 / 405051-44
> Fax: 030 / 405051-19
>
> Amtsgericht Berlin-Charlottenburg - HRB 93818 B
> Geschäftsführer: Peer Heinlein - Sitz: Berlin
>
>
Mit freundlichen Grüßen,

Stephan Seitz


--
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

https://www.heinlein-support.de

Tel: 030 / 405051-44
Fax: 030 / 405051-19

Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin

Re: Update default template from CentOS 5.5 to CentOS 7

[Dag Sonstebo]

+1 for updating to CentOS7
-1 for Machinina – they are great for quickly spinning up a basic VM, but 
personally I find them too limited when I want to just get a VM up and quickly 
install some tools for a demo or test.

Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue

On 10/07/2018, 21:08, "Daan Hoogland"  wrote:

how about the macchinina images as build in? At least for development those
are very convenient.

On Tue, Jul 10, 2018 at 9:59 PM, Gabriel Beims Bräscher <
gabrasc...@gmail.com> wrote:

> You are right Rafael, I was not clear with the "*(KVM)*". The idea would 
be
> to update others as well ;)
>
> 2018-07-10 16:34 GMT-03:00 Rafael Weingärtner  >:
>
> > That looks a good idea, to at least, update the current default template
> > that we ship in. However, we should update not only the KVM template, 
but
> > also XenServer and VMware, right?
> > Can we host image for these operating systems? The CentOS 5.5 images are
> > being hosted at http://download.cloudstack.org.
> >
> > On Tue, Jul 10, 2018 at 4:22 PM, Gabriel Beims Bräscher <
> > gabrasc...@gmail.com> wrote:
> >
> > > Hello,
> > >
> > > I would like to propose updating our current default VM template
> "CentOS
> > > 5.5(64-bit) no GUI (KVM)" to a newer version (e.g. CentOS 7). I also
> > think
> > > that we could benefit from a wider set of templates offering also
> Debian,
> > > Ubuntu, and Fedora.
> > >
> > > Cheers,
> > > Gabriel.
> > >
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>



-- 
Daan



dag.sonst...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: _configDao.isPremium() please help where this information comes from.

[Stephan Seitz]

Hey Boris!

This isn't the problem, just setting

mvn install -P deps -Dnoredist -Dnonoss; # this target doesn't work

export ACS_BUILD_OPTS="-Dnoredist -Dnonoss"; dpkg-buildpackage

I don't know what's the difference between noredist and nonoss.


Anyway if I do build the packages with noredist (which is mentioned way more 
often than nonoss in different documentations / Install.txt's), 
I do not know how to include the respective *jar's getting baked into the 
systemvmtemplate. Otherwise the cloud service won't start and no further
configuration of the systemvm will take place. Say: it won't connect to the 
management.

I'm currently using tools/appliance -> build.sh systemvmtemplate, but afaik, 
these scripts doesn't honor noredist?




Am Mittwoch, den 11.07.2018, 07:03 + schrieb Boris Stoyanov:
> Hi Stephan,
> 
> have you tried:
> mvn clean install -P developer,systemvm -D noredis
> 
> here’s more info 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack
> 
> Bobby.
> 
> 
> boris.stoya...@shapeblue.com 
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>   
>  
> 
> On 10 Jul 2018, at 18:19, Stephan Seitz 
> mailto:s.se...@heinlein-support.de>> wrote:
> 
> Thanks for your feedback! Do you know how to build the systemvmtemplate w/ 
> noredist? I didn't find
> anything regarding that in tools/appliance, also cwiki keeps quiet about that.
> 
> Thanks!
> 
> Stepnan
> 
> Am Dienstag, den 10.07.2018, 07:38 -0700 schrieb Frank Maximus:
> That setting is part of a property file of
> cloudstack-plugin-hypervisor-vmware.
> Most likely you are using a system build with noredist.
> In that case you also need a systemvm build that way.
> 
> Kind Regards,
> Frank
> 
> On Tue, Jul 10, 2018 at 12:16 PM Stephan Seitz 
> mailto:s.se...@heinlein-support.de>>
> wrote:
> 
> 
> Hi there,
> 
> Upgrading 4.11.0 to 4.11.1 we found an interesting problem in our (well
> played) staging infrastructure.
> 
> During SSVN provisioning, a somewhat "premium" configuration is detected
> (well we're using noredist since ... ever?).
> So the SSVM is configured with
>   resource=com.cloud.storage.resource.PremiumSecondaryStorageResource
> instead of
> 
> resource=org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource
> 
> In fact this particular setup always used (and should further use) simple
> NFS as Secondary Storage.
> 
> Sorry, but I can't find the real source
> of com.cloud.configuration.dao.ConfigurationDao#isPremium() and how to set
> this to false.
> 
> If anyone could shed some light?
> 
> 
> Thank You!
> 
> 
> 
> 
> Mit freundlichen Grüßen,
> 
> Stephan Seitz
> 
> 
> --
> Heinlein Support GmbH
> Schwedter Str. 8/9b, 10119 Berlin
> 
> https://www.heinlein-support.de
> 
> Tel: 030 / 405051-44
> Fax: 030 / 405051-19
> 
> Amtsgericht Berlin-Charlottenburg - HRB 93818 B
> Geschäftsführer: Peer Heinlein - Sitz: Berlin
> 
> 
> Mit freundlichen Grüßen,
> 
> Stephan Seitz
> 
> 
> --
> Heinlein Support GmbH
> Schwedter Str. 8/9b, 10119 Berlin
> 
> https://www.heinlein-support.de
> 
> Tel: 030 / 405051-44
> Fax: 030 / 405051-19
> 
> Amtsgericht Berlin-Charlottenburg - HRB 93818 B
> Geschäftsführer: Peer Heinlein - Sitz: Berlin
> 
> 
Mit freundlichen Grüßen,

Stephan Seitz


--
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

https://www.heinlein-support.de

Tel: 030 / 405051-44
Fax: 030 / 405051-19

Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin



signature.asc
Description: This is a digitally signed message part

Re: RE Update default template from CentOS 5.5 to CentOS 7

[Rohit Yadav]

While the documentation may say it supports older hypervisors, we can remove 
hypervisors that have reached end of life. I think if consider that, most 
support hypervisors (XS 6.5+, KVM el6+/ubuntu14.04+ and VMware 55u3+) with 
latest patches applied would support CentOS7, perhaps a hack could be used to 
register them as other linux 64-guest or as centos6.


We can attempt to officially say/deprecate the older hypervisors, for 4.12 we 
can aim to publish a new centos7 as default guest template (along with a Ubuntu 
18.04 template, so each new cloudstack env has two of the most popular distros).


- Rohit






From: Sateesh Chodapuneedi 
Sent: Wednesday, July 11, 2018 12:26:49 PM
To: dev@cloudstack.apache.org
Subject: RE Update default template from CentOS 5.5 to CentOS 7

While it's good idea to bump up the current default VM template "CentOS 
5.5(64-bit) no GUI (KVM)" to a newer version. I doubt the candidate would be 
CentOS 7. Reason being the supportability of the hypervisor. The candidate 
should be supported across all the versions of hypervisors that next version of 
CloudStack would support. To support CentOS 7 we might have to drop support for 
few of the versions listed below.

From 4.11 documentation the minimum versions supported are,
XenServer versions 6.1, 6.2 SP1, 6.5, 7.0, 7.1, 7.2 with latest hotfixes
VMware versions 5.0 Update 3, 5.1 Update 3, 5.5 Update 3b, 6.0 Update 2, and 
6.5 GA

Regards,
Sateesh

-Original Message-
From: Gabriel Beims Bräscher 
Reply-To: "dev@cloudstack.apache.org" 
Date: Wednesday, 11 July 2018 at 00:52
To: dev 
Subject: Update default template from CentOS 5.5 to CentOS 7

Hello,

I would like to propose updating our current default VM template "CentOS
5.5(64-bit) no GUI (KVM)" to a newer version (e.g. CentOS 7). I also think
that we could benefit from a wider set of templates offering also Debian,
Ubuntu, and Fedora.

Cheers,
Gabriel.


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

Re: _configDao.isPremium() please help where this information comes from.

[Boris Stoyanov]

Hi Stephan,

have you tried:
mvn clean install -P developer,systemvm -D noredis

here’s more info 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack

Bobby.


boris.stoya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

On 10 Jul 2018, at 18:19, Stephan Seitz 
mailto:s.se...@heinlein-support.de>> wrote:

Thanks for your feedback! Do you know how to build the systemvmtemplate w/ 
noredist? I didn't find
anything regarding that in tools/appliance, also cwiki keeps quiet about that.

Thanks!

Stepnan

Am Dienstag, den 10.07.2018, 07:38 -0700 schrieb Frank Maximus:
That setting is part of a property file of
cloudstack-plugin-hypervisor-vmware.
Most likely you are using a system build with noredist.
In that case you also need a systemvm build that way.

Kind Regards,
Frank

On Tue, Jul 10, 2018 at 12:16 PM Stephan Seitz 
mailto:s.se...@heinlein-support.de>>
wrote:


Hi there,

Upgrading 4.11.0 to 4.11.1 we found an interesting problem in our (well
played) staging infrastructure.

During SSVN provisioning, a somewhat "premium" configuration is detected
(well we're using noredist since ... ever?).
So the SSVM is configured with
  resource=com.cloud.storage.resource.PremiumSecondaryStorageResource
instead of

resource=org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource

In fact this particular setup always used (and should further use) simple
NFS as Secondary Storage.

Sorry, but I can't find the real source
of com.cloud.configuration.dao.ConfigurationDao#isPremium() and how to set
this to false.

If anyone could shed some light?


Thank You!




Mit freundlichen Grüßen,

Stephan Seitz


--
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

https://www.heinlein-support.de

Tel: 030 / 405051-44
Fax: 030 / 405051-19

Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin


Mit freundlichen Grüßen,

Stephan Seitz


--
Heinlein Support GmbH
Schwedter Str. 8/9b, 10119 Berlin

https://www.heinlein-support.de

Tel: 030 / 405051-44
Fax: 030 / 405051-19

Amtsgericht Berlin-Charlottenburg - HRB 93818 B
Geschäftsführer: Peer Heinlein - Sitz: Berlin

RE Update default template from CentOS 5.5 to CentOS 7

[Sateesh Chodapuneedi]

While it's good idea to bump up the current default VM template "CentOS 
5.5(64-bit) no GUI (KVM)" to a newer version. I doubt the candidate would be 
CentOS 7. Reason being the supportability of the hypervisor. The candidate 
should be supported across all the versions of hypervisors that next version of 
CloudStack would support. To support CentOS 7 we might have to drop support for 
few of the versions listed below.

From 4.11 documentation the minimum versions supported are,
XenServer versions 6.1, 6.2 SP1, 6.5, 7.0, 7.1, 7.2 with latest hotfixes
VMware versions 5.0 Update 3, 5.1 Update 3, 5.5 Update 3b, 6.0 Update 2, and 
6.5 GA

Regards,
Sateesh
 
-Original Message-
From: Gabriel Beims Bräscher 
Reply-To: "dev@cloudstack.apache.org" 
Date: Wednesday, 11 July 2018 at 00:52
To: dev 
Subject: Update default template from CentOS 5.5 to CentOS 7

Hello,

I would like to propose updating our current default VM template "CentOS
5.5(64-bit) no GUI (KVM)" to a newer version (e.g. CentOS 7). I also think
that we could benefit from a wider set of templates offering also Debian,
Ubuntu, and Fedora.

Cheers,
Gabriel.


DISCLAIMER
==
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.