i don't think i've seen that nick before either
oh that was hours ago
wow just reloaded my serial console ssh access menu, suddenly we have service names showing up, awesome!
if you have a vps, click on the vps in the service list, and then when it has the service detail page, click 'edit service label' .. once edited, you can see the label in the 'code|service|amount|recurring' table of one row. In the Service column mine reads 'OpenBSD VPS, 0.v'
on the serial console the columns are labeled 'ID|UUID|Name'
for the same system I see under the Name column 'free-daemon-consulting, 0.v'
the service label being present at the serial console really helps me, otherwise I have 4 vps'en and I'd hate to shutdown/boot the wrong one; sofar I have been consulting a local lookup table of uuid's vs system names, but having the service label for me avoids this extra step and makes things more likely to be error free
696 days uptime ... seems pretty stable :D
about time to upgrade that OpenBSD perhaps :D
man i'm behind, lots of scrollback...
codecaver: "It would be great if two nodes running Haproxy could share the public-facing IP." <-- you can certainly configure it that way on our platform, not sure what the consequences will be though of same IP on two different hosts within same VLAN
up_the_irons: Cool! Glad to know that's a possibility with your platform. Would you have an alternative suggestion for creating a load-balancer without a single point of failure?
jbergstroem: gotta give me a couple days for the SSD to arrive (need to order it), then like 24 hours for provisioning
toddf: yeah, those are there now (i announced it in here a few days ago); however, label updates are not real-time (still need to do that)
codecaver: like toddf said, OpenBSD and carp is a pretty good solution.  Not sure how familiar you are with OpenBSD though.
codecaver: there's also Linux and LVS: http://www.linuxvirtualserver.org/
up_the_irons: Right, so the same scenario of two nodes with the same public-facing IP, but both are OpenBSD boxes with CARP running. That sounds like a good idea to me. Would those both need to be dedicated boxes or could I rent a VPS for that portion? Rolling OpenBSD isn't a problem. I prefer it over Linux when possible.
codecaver: everything we're talking about is fully supported on our VPS platform, but I won't stop you if you want a dedicated box ;)
Sweet, really glad to hear that. I'm very impressed with your system, and definitely plan to migrate as much as possible to you when my project timeline allows. That said, I have one client who is interested in pricing out a geographically dispersed architecture, so about 2-3 boxes in CA and 2-3 boxes on the East Coast. I was thinking about going with ARPNetworks for the CA based deployment, and then possibly choosing a local (Florida) center for th
right-coast deployment, but do you have relationships or special WAN links to any other data centers that I should be aware of?
codecaver: awesome, i'm glad you like our architecture.  we do not have any special relationships with east coast data centers or MPLS links, but if you get into a DC / provider that also peers with someone we peer with, then the traffic would be "more direct".  Our peering list is here: http://arpnetworks.com/peering
up_the_irons: Great, thanks for the tip on that. I'll be sure to try and find someone with a common peer if we move forward with that plan.
:)
often just one or two hops
I really want to open up an east coast location, there's a lot of demand for geographic diversity...  <sigh>...  so many projects, so little time
and so few up_the_irons'
lol
hm looks like the best I can com up with is 4 hops :/
up_the_irons: One other outstanding question. . .I'm seriously considering a migration to an Illumos-based distribution for all of our deployed web and database servers. Would it be difficult to get an iSO setup for OmniOS (http://omnios.omniti.com/) or SmartOS (http://smartos.org/)? I noticed that the ISO list on your site said to simply contact if there was an unlisted distro needed.
ISO links are simple enough:
http://omnios.omniti.com/wiki.php/Installation
http://wiki.smartos.org/display/DOC/Download+SmartOS
This would probably be a summer/fall project for me.
up_the_irons: since you asked, mtr's from another host to ARP v4 https://dl.dropboxusercontent.com/u/3167967/screenshot_2013-05-13_10-37-39.png
and v6 https://dl.dropboxusercontent.com/u/3167967/screenshot_2013-05-13_10-38-32.png
codecaver: yes, that's no problem.  i can think of several customers who run solaris-based OS'
brycec: awesome!
tnx
np
codecaver: i don't know about smartos though, since it is really meant to be run on bare hardware and then VMs built from there.  You could run it on our dedicated boxes though, for sure
oh since the general topic came up
up_the_irons: Awesome, glad to hear that. And yeah, both SmartOS and OmniOS are intended to run on bare metal, so these would definitely be dedicated servers. Still on the fence about the switch (coming from RHEL/FreeBSD), but I'm starting to fall in love with Illumos. Zones, first-class Dtrace support, Crossbow, ABI/SVM…It's a compelling technology stack, but a steep learning curve.
I note that there appares to be no VMX/VMM flags on cpus in my kvm instances. I presume that means we're not permitted to try to nest vms. ;-)
I'm sure you're allowed to try, toddf, but you might not be very successful :p
toddf: i believe > kvr27 do support nesting, but i've never tried it
brycec: "Major Topic" LOL
codecaver: yeah i've been meaning to play with SmartOS for a while now; it looks really cool
I recently started playing with FreeBSD jails and it's a lot of fun
up_the_irons: Seems like network virtualization features of Crossbow might be something you would benefit from internally. I haven't had the chance to use it yet, but from what I understand you're able to do full-stack network virtualization, and that includes creating VLANs and QoS configurations.
codecaver: yeah, sounds interesting
codecaver: just don't break QinQ support ;-) *grin*
heh
toddf: Where's the fun in deploying new technologies if you don't get to break existing ones? ;)
/5/
grr
codecaver: at least the smartos installations I have also assume you install smartos to a usb drive (and boot from that), so every time you'd want to update smartos, you would also want to update that usb drive
they bake new smartos images bi-weekly
jbergstroem: That seems less than ideal. There isn't a net-install option with PXE or some-such? I know OmniOS supports that.
codecaver: it saves a config on your "physical" device, then use the rest of that for your zones. i don't think smartos will care too much about how you boot it as long as you can write back to that device whenever you want to update it
jbergstroem: Interesting. Have you had a chance to play with it or any of the other Illumos distributions much yet? As mentioned earlier, I'm still considering a migration. . .I just get the feeling that doing so will leave a trail of tears due to the lack of documentation/community support. . .
codecaver: have been running smartos for about a year locally. use it to deploy vm's with buildbot clients
can't say i've felt abundance of docs. their wiki has most stuff you need, sun/illumos has man pages for most stuff and so does the smartos specific things such vmadm/dsadm/etc
jbergstroem: Nice.
jbergstroem: Did you come from a Solaris background prior to working with SmartOS?
codecaver: no solaris background, just general tinkering
https://www.smore.com/clippy-js