Hi guys,
just sorting out our repository.
Maybe you find it useful:
https://github.com/HeinleinSupport/acs-template-scripts
Currently, the scripts are looking somewhat messy and our SuSE LEAP
scripts are waiting for cleanup, but for the impatient ones ...
For ACS we're moving to public github p
CentOS7, Cloudstack 4.7.
Log management server:
2016-02-18 12:29:11,412 DEBUG [c.c.a.ApiServlet]
(catalina-exec-1:ctx-b584fb48 ctx-a3bf9246) (logid:4f89e2ee) ===END===
10.30.10.41 -- GET
command=addImageStore&response=json&name=%D0%A8%D1%8C%D1%84%D0%BF%D1%83%D1%8B&provider=S3&details%5B2%5D.k
Hi Stephan,
First of all, thanks for scripts, also can you let me know what need to be
executed on VM after script file's are copied on VM.
I don't see any information, is like only copy the files and execute
newtemplate.sh.
Regards,
Cristian
On 19.02.2016 13:19:47, Stephan Seitz
wrote:
Hi,
Last I enabled HTTPS for the console VM, I had to get a *.domain.tld and a
wildcard certificate to match that.
Is there no other way to enable SSL without the wildcard DNS bit?
It adds a bit of overhead having to setup DNS infra for the customer just so
he's able to securely access his cloud
Hey Cristian,
we will add distribution-dependent README.md next week.
If you'ld like to follow the same naming, just:
1. create a user "vmadmin"
2. optional: add vmadmin user to sudoers (maybe with NOPASSWD: )
3. copy the files
4. enable the init scripts. E.g. systemctl enable cloud... or
update
Hi,
well, one could manage huge hosts-files ;)
but seriously, you just need a dns-name / wildcard-certificate for a
domain you trust. If your customers trust your certificate AND your dns
- maybe because of dnssec - you don't need that for every customer.
To keep things off our full-featured nam
Hi Stephan,
I just figured out how to do, i also created a template for CentOS 7 but i
changed user from vmadmin to root also everything is ok except i'm not able to
connect via ssh on VM ( i get time out ) but if go via console on VM i have
network connection and generated password works.
So there's no way around it, thanks Stephan. :-)
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Stephan Seitz"
> To: users@cloudstack.apache.org
> Sent: Friday, 19 February, 2016 16:21:37
> Subject: Re: HTTPS for console VM, without
Stephan,
Sorry, after VM restart SSH works.
Regards,
Cristian
On 19.02.2016 18:14:43, Stephan Seitz
wrote:
Hey Cristian,
we will add distribution-dependent README.md next week.
If you'ld like to follow the same naming, just:
1. create a user "vmadmin"
2. optional: add vmadmin user to sudoer
Hello guys, we have a problem, we need to limit the Network-rate for the all
VM’s on a specific account the bandwidth require for the client its 2Mb, which
parameters in offering (Compute, system, disk, network) do I need to change in
order to apply the limit?.
Thanks
Cordialmente / Best r
One way to accomplish this would be to set rate limit on Network offering (in
UI, the label for that parameter is “Network Rate (Mb/s)”) that would be used
specifically to create network/s specific to that particular account.
Regards,
Somesh
From: Yesid Mora [mailto:ym...@o4it.com]
Sent: Friday
You could probably hack this - if you only provided enough IPs for your System
VMs so that it’s IP wouldn’t change, you could register the SSL cert for that
specific FQDN.
Seems like it should be possible to have the console proxy run in http-only,
then put an TLS endpoint in front of it (hapro
Yeah, it's a hassle.
I wish the console VM came with a self signed certificate by default and be
accessed via https by default.
Nowadays I use your proxy-ing tip to quickly put the cloudstack management
behind mod_ssl - way easier than having to mess with Tomcat, however browsers
will not rend
13 matches
Mail list logo
