• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "My future in 'the cloud'"

Collapse

  • fool
    replied
    Originally posted by Jefferson View Post
    However, IaaS generally turns out to be more expensive than on-premise and with caveats regarding availability. E.g Azure will only honour SLA's on IaaS VM's if they are deployed in at least redundant pairs.
    I suspect this is generally only true when doing a fairly shallow comparison.

    Sure, it you've got a single rack maxed it's going to be cheaper than the compute from AWS. That's not all you're paying them for though.

    Can you do 3 datacentres, massive interconnects, autoscaling and failover with spare capacity and all the things and more importantly people those things entail? No, you probably can't, not unless you're very big and at that point amazon will cut you a deal.

    Even if you're being cheap and don't care that much about the reputation hits that downtime will give you, the dev/ops time saved in itself probably pays for AWS.


    P.S. Don't take this the wrong way, it's not intended to disparage. I'm just attempting to point out where the value actually lies as otherwise it's hard to decipher as buzzword overusage muddys the water.
    Last edited by fool; 6 November 2015, 17:39.

    Leave a comment:


  • Jefferson
    replied
    Originally posted by reddog View Post
    this is true, and i will start of by doing this. However my thinking is that in the end in order to have lots of automation, and hence lots of savings, companies won't simply replicate their existing IT infrastructure in the cloud (sort of IaaS), they will end up going down the PaaS route. Anyone got any experience of this, are most blue chips just at the stage of experimenting with lift bits of their infrastructure into the cloud without much modification?
    I think at the moment a lot of companies are moving to SaaS products such as Office 365 and experimenting with bits of their infrastructure in the cloud (IaaS).
    However, IaaS generally turns out to be more expensive than on-premise and with caveats regarding availability. E.g Azure will only honour SLA's on IaaS VM's if they are deployed in at least redundant pairs.

    I think the future will be based more around PaaS as this offers greater savings and features e.g autoscaling of web servers.
    This will require a lot of redesign for existing applications before they can be moved to this model.

    I would say getting up to speed on Azure / AWS combined with traditional skills would definitely put you in a strong position going forward.

    Leave a comment:


  • fool
    replied
    It depends what you're doing but using a PaaS either removes versatility or won't do the same job as your IaaS. They tend to offer you hosted services for your data layers so you can outsource the problem, which is fine if you want to be a low paid monkey or a developer doing ops as a side gig happy choosing only a subset of blessed tech.

    Anyhoo, the drive towards automation is about running apps at scale. It goes right back to my previous comment which was "cattle not pets" which means, yes you do need them sysadmin skills, but also you need to be able to write code to implement those skills on 1000s of servers that go away and come back at random.

    If you want to take it a step further, start talking about service discovery and frameworks such as mesos or kubernetes. These will offer a PaaS like experience with the versatility of being able to roll and automate your own data stores.

    Leave a comment:


  • gables
    replied
    Originally posted by reddog View Post
    this is true, and i will start of by doing this. However my thinking is that in the end in order to have lots of automation, and hence lots of savings, companies won't simply replicate their existing IT infrastructure in the cloud (sort of IaaS), they will end up going down the PaaS route. Anyone got any experience of this, are most blue chips just at the stage of experimenting with lift bits of their infrastructure into the cloud without much modification?
    I'd be interested in the state of play, or stages if you like. I imagine there'll be a spread of what's been done, it would be interesting to understand what that looks like.

    We had a session with our provider who suggested that a lot\number of firms who had gone the outsourcing route were now re-employing technical staff but leaving the infrastructure in the cloud.

    Leave a comment:


  • reddog
    replied
    Originally posted by gables View Post
    This ^^

    If the firm are moving to cloud infrastructure, like we have here, then as said above the normal datacentre operations need to be performed. But, additional considerations have to be made like how you access the infrastructure\security, supplier (amazon) management and SLAs etc am0ongst others.
    this is true, and i will start of by doing this. However my thinking is that in the end in order to have lots of automation, and hence lots of savings, companies won't simply replicate their existing IT infrastructure in the cloud (sort of IaaS), they will end up going down the PaaS route. Anyone got any experience of this, are most blue chips just at the stage of experimenting with lift bits of their infrastructure into the cloud without much modification?

    Leave a comment:


  • gables
    replied
    Originally posted by fool View Post
    Maybe but if you're playing the game right, they're cattle not pets.

    In that vein, learn cloudformation. Use ELBs, LaunchConfiguration and Autoscaling Groups. Do that over 3 zones and stop logging into the boxes and you're a baby cloud engineer.
    That's me told

    Leave a comment:


  • MrMarkyMark
    replied

    Leave a comment:


  • fool
    replied
    Originally posted by gables View Post
    This ^^

    If the firm are moving to cloud infrastructure, like we have here, then as said above the normal datacentre operations need to be performed. But, additional considerations have to be made like how you access the infrastructure\security, supplier (amazon) management and SLAs etc am0ongst others.
    Maybe but if you're playing the game right, they're cattle not pets.

    In that vein, learn cloudformation. Use ELBs, LaunchConfiguration and Autoscaling Groups. Do that over 3 zones and stop logging into the boxes and you're a baby cloud engineer.

    Leave a comment:


  • gables
    replied
    Originally posted by SpontaneousOrder View Post
    linux boxes on AWS still need administering.
    This ^^

    If the firm are moving to cloud infrastructure, like we have here, then as said above the normal datacentre operations need to be performed. But, additional considerations have to be made like how you access the infrastructure\security, supplier (amazon) management and SLAs etc am0ongst others.

    Leave a comment:


  • SpontaneousOrder
    replied
    linux boxes on AWS still need administering.

    Leave a comment:


  • northernladuk
    replied


    HTH...

    Leave a comment:


  • LondonManc
    replied
    Read up on AWS and how it works, then assess whether that sort of model works for you in terms of it being the sort of environment that you want to work in.

    Leave a comment:


  • SueEllen
    replied
    How long is a piece of string?

    Seriously you have answered your own question.

    Leave a comment:


  • oliverson
    replied
    Originally posted by reddog View Post
    (Wasn't sure whether to post this in Technical, but I thought business was more appropriate)

    My Past and Present: I have contracted for quite a few years as a Linux / Unix sysadmin, but in my current long running contract I have been doing more DevOps / Environment management.

    My Future: I was planning to get back into Linux / Unix admin when my current project ends, and thought about taking a RedHat Cert to get me fully up to speed. However I recently found out that a major financial institute that I used to contract for is gradually moving from onsite infrastructure to Amazon Web Services. This was a bit of a surprise, as I didn’t expect off premises cloud computing to hit financial services so soon. But in all honesty, this sort of outsourcing makes a lot more sense than the usual offshoring BS.

    My Question: Looks like the days of the classic Unix / Linux sysadmin are numbered. How should I approach my transitions to ‘the cloud’ (a term that seems to mean different things to different people). I was thinking of going through the Redhat Certification course material, but practice on Amazon Cloud Infrastructure instead of a local PC as an entry point. However I am open to any other suggestions. (I am conscious I may just replicating the same old processes, but on cloud infrastructure, I guess moving away for many people will be a challenge going forward).

    Leave a comment:


  • reddog
    started a topic My future in 'the cloud'

    My future in 'the cloud'

    (Wasn't sure whether to post this in Technical, but I thought business was more appropriate)

    My Past and Present: I have contracted for quite a few years as a Linux / Unix sysadmin, but in my current long running contract I have been doing more DevOps / Environment management.

    My Future: I was planning to get back into Linux / Unix admin when my current project ends, and thought about taking a RedHat Cert to get me fully up to speed. However I recently found out that a major financial institute that I used to contract for is gradually moving from onsite infrastructure to Amazon Web Services. This was a bit of a surprise, as I didn’t expect off premises cloud computing to hit financial services so soon. But in all honesty, this sort of outsourcing makes a lot more sense than the usual offshoring BS.

    My Question: Looks like the days of the classic Unix / Linux sysadmin are numbered. How should I approach my transitions to ‘the cloud’ (a term that seems to mean different things to different people). I was thinking of going through the Redhat Certification course material, but practice on Amazon Cloud Infrastructure instead of a local PC as an entry point. However I am open to any other suggestions. (I am conscious I may just replicating the same old processes, but on cloud infrastructure, I guess moving away for many people will be a challenge going forward).

Working...
X