hrm
CaZe: k
can anybody help me with adding an aditional core to a vm?
jbergstroem: have you sent a support ticket yet?  we like to have those for tracking...
oh, sorry about that. irc is just too convenient
jbergstroem: yeah, it's just that we don't get notified of any request you ask in irc, but we do if a ticket is opened
IRC to RT email!
lol
jbergstroem: what kind of load balancing are you referring to?  disparate networks, VRRP, cold standby's... ?
jbergstroem: (bringing your question in the public channel b/c others may have the same question)
very really real problems
qbit: say wut
VRRP
qbit: hahaha
yeah i'm trying to avoid it, or perhaps do it only on special request.  we've been experimenting with different setups / scenarios.  VLAN pre-built on separate router, but shutdown, and a manual "failover" is probably the way we're gonna go
up_the_irons: kind of open for discussion tbh. manual failover with own-implemented heartbeat/similar would be fine as a start
jbergstroem: if you have a /29 or larger and would want VRRP, we could probably set that up for you (the equipment is almost in place, just haven't set up VRRP yet).  there are probably better scenarios if you are willing to go beyond the traditional "single gateway" model, such as taking 2 default routes from us (would be terminated on separate routers, obviously), or even doing like ibgp or
ospf
if you have 2 VMs in a VLAN, would be easier to fail the IP between them
or are we not talking about host redundancy, but upstream network?
it really comes down to what level of complexity you want and where the balance is between that complexity vs. uptime coupled with the fact that complexity can obviously lead to downtime in and of itself
at the moment my main 'concern' is host redundancy
josephb: i think jbergstroem means upstream network
oh, n/m
upstream wise i haven't really looked into yet
jbergstroem: two VMs with CARP, or keepalivd, etc... might work
up_the_irons: yep, probably doing that. just wanted to ask what kind of infrastructre you had for that. some other hosts i used had those virtualized routers/switches from juniper (ex42xx right?) which allowed me to do moar things through there.
i should make my irc bot all distributedie
error: unable to create temporary sha1 filename : No space left on device
error: unable to create temporary sha1 filename : No space left on device
ewps
stupid inodes
and not manyofthem
jbergstroem: VMs belonging to the same account are on the same private VLAN, so they have unfetered layer-2 access between them.  a little more detail is here: http://support.arpnetworks.com/kb/vps/are-private-ip-addresses-available-for-vps-to-vps-communication
jbergstroem: no juniper stuff over here, but if you want a specific protocol, let me know and i'll see if I can provide
up_the_irons: ok, thanks.
np