Slashdot Mirror

← Back to Stories (view on slashdot.org)

OpenStack Juno Released

Posted by samzenpus on from the check-it-out dept.

darthcamaro writes The OpenStack Juno release is now generally available. This the 10th major release for the open-source cloud platform and introduces the Sahara Data Processing Service as the major new project. That's not the only new feature in Juno though, with 310 new features in total. The new features include cloud storage policy, improved IPv6 support, a rescue mode and improved multi-cloud federation capabilities."

20 comments

  1. It is free! by Anonymous Coward · · Score: 0

    It has been set free!

    SPLAT!

  2. And OpenStack is...? by wonkey_monkey · · Score: 4, Informative

    (disclaimer: I already knew what OpenStack is)

    If you can't afford to waste the six extra words it would take to say "open-source cloud computing platform..." how about a Wikipedia link? It's what hypertext is for, after all.

    "Hurr, if you don't know what OpenStack is, you shouldn't be on Slashdot!"

    will no doubt be the refrain of some. Well, what's wrong with informing those who don't know? Or are we still supposed to jealously guard the Secret Knowledge?

    An inclusively written or well-linked summary is not an insult to anyone's intelligence or level of knowledge.

    --
    systemd is Roko's Basilisk.
    1. Re:And OpenStack is...? by Anonymous Coward · · Score: 0

      What the heck is a "cloud computing platform"?

      It's like Sealand, but up in the sky.

    2. Re:And OpenStack is...? by Anonymous Coward · · Score: 0

      I don't.

      I do however know what a Juno is http://en.wikipedia.org/wiki/Roland_Juno-106, and I have no idea what that has to do with cloud computing. With a remote system, you'll definitely get a noticeable delay.

    3. Re:And OpenStack is...? by Anonymous Coward · · Score: 0

      And what extra information would be conveyed by a Wikipedia link? If you don't know what XYZ is, Wikipedia is the obvious choice, and it's trivial to search Wikipedia for a keyword. Wikipedia and Google (LMGTFY) links should be banned from /. because they're just stating the obvious.

    4. Re:And OpenStack is...? by Anonymous Coward · · Score: 0

      So it's an idealistic utopia, that turns out to be not all that it's fans make it out to be, and is slowly rusting away?

    5. Re:And OpenStack is...? by larpon · · Score: 3, Funny

      how about a Wikipedia link?

      Link to OpenStack Wikipedia entry
      ... There, fixed that for you

    6. Re:And OpenStack is...? by Jawnn · · Score: 1

      Actually, if I can run all the magic on hardware that I control, it's every bit of that idealistic utopia. Oh, wait. That's virtualization, not "cloud technology". My mistake.

    7. Re:And OpenStack is...? by Anonymous Coward · · Score: 0

      It started off as a api driven vm orchestrator for NASA (nova) and an s3 compatible object store like s3 (swift) within Rackspace. After awhile, they joined forces. Nova and Swift were the first two components of Openstack. Subsequently keystone (for auth), glance (for image management) and then cinder (volume management, exposing raw disk partitions to a vm host by way of orchestring iscsi, ceph, etc) split off.

      Now Openstack is largely chasing Amazon's feature set, while heavily leveraging some pretty cutting edge stuff in the network layer. It's gaining some traction too in the enterprise world. VMware is adding a compatibility layer between openstack's management stuff. Nova and several components of openstack can already talk to Xenserver by way of Xen api. If you are virtualizing on kvm, you don't have much windows in your site, openstack makes a lot of sense, especially if you are in academia. However, upgrading openstack still requires some downtime. If you have multiple meta data servers using the same database for example, once you start the upgrade, if you upgrade, the first server, the binaries get touched, then changes to the database schema are applied, which means the other meta data servers that use that same database are hosed until you upgrade them as well.

  3. BrokenStack - Tsarkon Reports by Anonymous Coward · · Score: 1

    Only Redhat can save BrokenStack now.

    A bunch of fat, greasy stupid vaping ex D&D "hackers" writing shit code that never works.

    Now Redhat is trying to the adult in the room and fix it.

    I hope Kilo's new feature is that someone actually tested this shit and it works.

    Tsarkon Reports

    1. Re:BrokenStack - Tsarkon Reports by Anonymous Coward · · Score: 0

      OpenStack works for us, both Havana and Icehouse releases in use. Maybe the fault is with you.

    2. Re:BrokenStack - Tsarkon Reports by Anonymous Coward · · Score: 1

      No, two production clouds. No consultants used. Team of 2.

      No reliance on Canonical. All configured, tested and built using the standard documentation. we have written our own in-house install scripts. Part of a 2 year project that started before Grizzly. First implementation went live a year ago.

      With an attitude like that the fault is you.

    3. Re:BrokenStack - Tsarkon Reports by module0000 · · Score: 1

      OpenStack works fine - your lack of competency doesn't mean the project is shit. Read the docs (repeatedly) until your mind can wrap around it, or just ask someone for help.

      --
      Trackball users will be first against the wall.
    4. Re:BrokenStack - Tsarkon Reports by Anonymous Coward · · Score: 1

      Team of two, ran two DARPA funded projects using openstack. It worked pretty well. We largely leveraged Salt in the middle of the project, and then towards the end we used a lot more Ansible since it was simpler to kick off and be done with a small team of two and less than 200 physical servers.

      We had high availability as best as we could. The network node component is a sore point, as mac address and firewall rules cloning on the backend for seemless fallover looks pretty hard, but the new release is suppose to fix that.

      The projects started off in production in Essex though, and finally the projects were finished around August. I still run Icehouse at home and it's been a giant boon to quickly throwing up hadoop and the like using the python api and heat to orchestrate. Having ran it for 2ish years, I know it well enough, and have been able to write patches when something breaks, although someone always beats me to it when I try to submit my patch.

      You don't have to run it out of canonical, but that is actually the best supported distribution. Redhat buying Ceph and owning Gluster already could be a good tie in for clouds down the road, but that's neither here or there. If anything, Redhat unable to partner with anyone smaller than they are is going to be distruptive to Openstack down the road.

    5. Re:BrokenStack - Tsarkon Reports by Anonymous Coward · · Score: 1

      +1 to this. OpenStack isn't easy, and we went from OpenStack to CloudStack and back to OpenStack during our feasability stage. CloudStack was easier to get running, but couldn't do what we needed. OpenStack took a lot more effort, and we had to configure from scratch, bit by bit, until we got a system that did exactly what we wanted (functionality and technology wise). It's getting better with each release though (although every release seems to either break or deprecate something we're using, leading to a fair amount of re-engineering).

      If you want to point and click your way to a cloud, it's not for you. Not yet anyway. However, if you are prepared to put in the hard work (6 months of reading thousands of pages of documentation and building various iterations of a test system), it works and works well.

  4. network troubleshooting by Anonymous Coward · · Score: 0

    openstack is pretty easy to set up using packstack but I find the network configuration at post-install time confounding. Wish there was a selection of "canned" networking options to choose from for basic private clouds.

    1. Re:network troubleshooting by Anonymous Coward · · Score: 1

      From my experience OpenStack is an "all or nothing" product - you can either use a pre-rolled configuration and get what you are given, or spend a long time learning everything about it and hand-rolling your own to do what you want.

  5. tl;dr software for building clouds by nuonguy · · Score: 2

    Fine, I'll paste the link and summary you care about:

    http://www.openstack.org/softw...

    OpenStack Juno, the tenth release of the open source software for building public, private, and hybrid clouds has 342 new features to support software development, big data analysis and application infrastructure at scale. The OpenStack community continues to attract the best developers and experts in their disciplines with 1,419 individuals employed by more than 133 organizations contributing to the Juno release.

    Everything else is up to you now. Upvotes, please. :-)