Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/2022
Hi,
I'll remove the NICs. Thanks for the notification.
I assume I'll have to do the same for all my templates as I am using the
same script to generate the ova.
---
If your project
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1700
Wido,
Will do, but need to wait until next week to get some help re getting IPv6
on my test rig. As soon as I have feedback, I'll post here.
Lucian
--
Sent from
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1700
Thanks
I'd be happy to give this a run when all the bits are in then, @wido
@rhtyd if the orangutan could build some packages when the time comes,
that's be great. ;-)
---
If your
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1700
@wido As an IPv6 rookie I am trying to wrap my head around this.
Why can't we just DHCP out to instances a /128, in a similar manner we do
with IPv4?
Is this all to avoid too much code
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1692
Sorry guys, am unable to test currently and cannot LGTM code that I
obviously don't understand.
Hopefully a coder will step up shortly.
---
If your project is set up for it, you can reply
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1692
@serg38 Macchinina is 64bit.
In KVM I add it as "Other PV (64bit)", though adding it as CentOS or Debian
should also work.
---
If your project is set up for it, you can reply to
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1692
Sure, though I may not have the time to do it today, but soon.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1692
Can you guys let me know if this runs OK on all your HVs? I've rebuilt the
kernel
http://dl.openvm.eu/cloudstack/macchinina/x86_64/testing/
---
If your project is set up for it, you can
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1692
Hi guys, sorry this has caught me in my holidays so no ability to do
anything about it.
In the following week I'll work on a new minimal kernel with improved
support for VMware stuff
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1663
Thanks a lot for implementing this properly :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user NuxRo closed the pull request at:
https://github.com/apache/cloudstack/pull/1653
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1653
Understood, thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1653
So, you guys kind of lost me, all I want is my VRs not to be used in DNS
reflection attacks.
Do we have a go or does it break things? :)
---
If your project is set up for it, you can reply
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1653
@jburwell I am afraid I do not have the coding skills to do what you want
re that variable, I am just submitting @ustcweizhou's code from that Jira issue.
Right now basic/sg zones
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1653
Rohit unfortunately I do not have git setup properly, I am limited to what
the github interface offers me.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1653
Done?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1653
Rohit, done, go right ahead.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1653
I've tested this in Adv zone with Security Groups and it works. Can't vouch
for "pure" Adv zones. Perhaps @ustcweizhou can say more.
---
If your project is set up for it, you
GitHub user NuxRo opened a pull request:
https://github.com/apache/cloudstack/pull/1653
Prevent DNS reflection attacks
At least in SG zones DNS on the VR is publicly accessible and as such
susceptible to DNS amplification/reflection attacks. This fixes it as per
https
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1547
+1 merging, I'm also interested in this if it affects Advanced zone +
Security Groups.
Will test ASAP.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user NuxRo commented on the issue:
https://github.com/apache/cloudstack/pull/1582
I do run that service, but the templates could do with a bit more TLC,
especially the Debian/Ubuntu.
It could be a starting point though, for CentOS the kickstarts are public
in github
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-220984529
Thanks Daan,
Does that mean we're good to go?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-220033959
Thanks buddies.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-219870382
Meh, this PR really doesn't want to make the freeze.
Daan, any ideas?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-219459752
Right, had a closer look. That check fails due to env problems:
https://paste.fedoraproject.org/367164/12782146/raw/
i.e. "updatevirtualmachine f
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-219252770
Not right now, I can try to build some nested stuff next week and have a go
with that. I'll let you know.
---
If your project is set up for it, you can reply
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-219247683
Good job, if integration tests pass I'll start testing it as well as the
dynamic offering bit.
---
If your project is set up for it, you can reply to this email
GitHub user NuxRo reopened a pull request:
https://github.com/apache/cloudstack/pull/1520
CPU socket count reporting correction
CPU socket count reporting correction
From
https://github.com/MissionCriticalCloud/cosmic-plugin-hypervisor-kvm/pull/16
You can merge this pull
Github user NuxRo closed the pull request at:
https://github.com/apache/cloudstack/pull/1520
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user NuxRo reopened a pull request:
https://github.com/apache/cloudstack/pull/1520
CPU socket count reporting correction
CPU socket count reporting correction
From
https://github.com/MissionCriticalCloud/cosmic-plugin-hypervisor-kvm/pull/16
You can merge this pull
Github user NuxRo closed the pull request at:
https://github.com/apache/cloudstack/pull/1520
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-217857669
Same here.
Is this XenServer specific, can anyone with an XS test bed help?
---
If your project is set up for it, you can reply to this email and have your
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-217853178
Thanks Daan
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-217795687
Sorry to be a pain, but any updates on this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1520#issuecomment-217094836
I'd appreciate it if someone else could do it, I do not have the setup to
perform more advanced github operations right now, other than the UI.
---
If your project
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-216812806
Ah, indeed. It should be running the test against a Security Group zone,
not Adv.
---
If your project is set up for it, you can reply to this email and have your
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-216781424
Any idea why Travis fails that 1 job?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-21627
rhtyd,
You can test via cloudmonkey, e.g.
update virtualmachine id=937daff4-7ce8-454c-bc8b-6f96b72017f5
securitygroupids=db6b797f-5262-4be2-a3b1
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-215350363
Applied successfully to 4.8 and tested, it works fine as far as I could
tell, but the SG change operation goes through even if the VM is online, so
"CLOUDSTACK
GitHub user NuxRo opened a pull request:
https://github.com/apache/cloudstack/pull/1520
CPU socket count reporting correction
CPU socket count reporting correction
From
https://github.com/MissionCriticalCloud/cosmic-plugin-hypervisor-kvm/pull/16
You can merge this pull request
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1297#issuecomment-208318271
Daan,
How did you test?
I'm trying to apply the patch to either 4.8.0 or master and on neither it
does so cleanly:
Hunk #7 FAILED at 467.
1
Github user NuxRo commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1011#discussion_r52766006
--- Diff: tools/marvin/marvin/config/test_data.py ---
@@ -784,6 +784,18 @@
"format": "OVA",
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1281#issuecomment-166837966
+1
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1145#issuecomment-160904404
@wido yes https://github.com/apache/cloudstack/pull/1144 , just PR against
correct branch now
---
If your project is set up for it, you can reply to this email
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/985#issuecomment-160654716
Ok, godspeed.
With a bit of luck perhaps we'll see this somewhere in 4.7.x?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1038#issuecomment-157983748
+1 to merge on master
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user NuxRo commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1075#discussion_r45174353
--- Diff: packaging/package.sh ---
@@ -18,26 +18,37 @@
function usage() {
echo ""
-echo "usage: ./package.sh
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1038#issuecomment-157428042
Right, so what now?
Can't we just postpone this till 6.7 and perhaps provide some easy patches
in the meanwhile for whoever wants to use in 4.5 and 4.6
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1075#issuecomment-157328375
LGTM
I did a centos63 build and it worked as expected.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1044#issuecomment-155735899
On a second thought - and something worth pondering on - this could have
some security implications.
Imagine you have a private cloud, a developer/employee
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1044#issuecomment-155740283
Good point as well with the "unexpected". I definitely see where Wei is
coming from, but I think it could be misleading. Perhaps a better way to do
th
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1044#issuecomment-155751828
Ah, right, checking the code is important. :-D
I'll go back to my corner.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1027#issuecomment-155008717
Great stuff, +1 for having the channel enabled by default.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1044#issuecomment-154707648
Makes sense and looks good, but I am surprised you are still using these
scripts instead of cloud-init.
On the same note, worth having a look at how cloud-init
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1038#issuecomment-154692467
yeah baby!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1003#issuecomment-153643254
@koushik-das You are right, I did not realise the display name was missing
from there.
Can't we make that table a bit wider so we can add another column or two
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1003#issuecomment-153439504
That would help, I'm all for 100+ :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1003#issuecomment-153431622
@bhaisaab Thanks for that. The UI is indeed in need of attention.
The problem with listing the VMs is that the UI will only show a few, then
as you scroll
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/1029#issuecomment-153467987
Excellent! I thought this feature was already implemented via
expunge.delay, good to know it doesn't work as I thought it was.
---
If your project is set up
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/962#issuecomment-150537570
@Snuf is there a list of all hv gurus? I'd like to exclude all of them (bar
kvm), see if that helps.
---
If your project is set up for it, you can reply
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/954#issuecomment-150545386
I can confirm Wei's modifications fixes my problem.
Both operations (create tmpl and create vol from snapshot) succeed with
RPMs built from https://github.com
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/954#issuecomment-150638003
Count it, but @karuturi gave me the impression she was going for a
different kind of fix, on the ovm3 side of things, might want to check with her.
---
If your
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/962#issuecomment-150225444
I've built EL6 RPMs from
https://github.com/snuf/cloudstack/archive/6efe627e8e11c18acf62ff02b85007de122a917c
and "yum reinstall" management and agent.
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/954#issuecomment-149896726
Wei,
These operations are done on a snapshot of a ROOT volume that does not
exist any more.
That VM has long been deleted, but the snapshot is OK
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/954#issuecomment-149905640
So to clarify:
FAIL - create volume from snapshot whose original volume has been deleted
PASS - create volume from snapshot whose original volume has
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/954#issuecomment-149887192
I used ovm3 initially and now I tried with ovm3guru, no luck, both
operations fail (create volume, create template).
---
If your project is set up for it, you can
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/954#issuecomment-149890722
Ovm3Guru made a difference! I could create a template from the snapshot,
however not a volume.
Here's the error I got when trying to create a volume:
http
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/954#issuecomment-149876303
BTW excluding ovm3 in hypervisor.gurus.exclude doesn't fix anything for me.
The problem remains.
I'll re-build with Wei's patches and test.
---
If your project
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/934#issuecomment-148631542
@karuturi sure, it was a normal, standard installation via the web UI on
CentOS6 HVs and mgmt, no automation.
---
If your project is set up for it, you can reply
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/934#issuecomment-148469676
@karuturi Tested, it works! Thanks!
I'm happy with this so far.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user NuxRo closed the pull request at:
https://github.com/apache/cloudstack/pull/175
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user NuxRo opened a pull request:
https://github.com/apache/cloudstack/pull/175
use eu.ceph.com as ceph.com is down
Same change as in
https://github.com/apache/cloudstack/commit/05e4ba7350e7da36e3b9511d5e987c84b0be7ab5
You can merge this pull request into a Git repository
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/165#issuecomment-92782014
Do note there are slight differences between EL7 ifconfig output and EL6.
Since we're making changes, +1 for ip, ifconfig might not even be
available at all
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/140#issuecomment-8641
Looks OK to me, waiting for a dead NFS connection is a PITA.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user NuxRo commented on the pull request:
https://github.com/apache/cloudstack/pull/86#issuecomment-75929910
Daan,
Sure, that works for me. Or Instance scaled to the requested offering.
---
If your project is set up for it, you can reply to this email and have your
GitHub user NuxRo opened a pull request:
https://github.com/apache/cloudstack/pull/86
Update messages.properties
Instances ca be scaled up or down, no only up.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NuxRo/cloudstack
GitHub user NuxRo opened a pull request:
https://github.com/apache/cloudstack-docs-rn/pull/3
Update rnotes.rst
corrected small typos regarding version numbers
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/NuxRo/cloudstack-docs
77 matches
Mail list logo
