Updates from December, 2015 Toggle Comment Threads | Keyboard Shortcuts

  • penguin 17:32 on 2015-12-25 Permalink | Reply  

    Mac software essentials 

    Well, after the Firefox Essentials, here’s my list of Mac essentials:

     
  • penguin 17:22 on 2015-12-23 Permalink | Reply
    Tags: firefox,   

    My essential Firefox addons 

    … can be seen on the Firefox Addons page as collection 🙂 .

    The addon ecosystem of Firefox is what keeps me with it. And the way it’s done. One example: Mouse Gestures are available on Chrome, which seems to be a lot faster and smoother today :'( … but in FF, when I go to the settings page, I can still use mouse gestures, cause it’s just another page.

    In Chrome I can’t. I like the Firefox behavior – it’s consistent, which is highly a highly underrated property these days.

     
  • penguin 12:27 on 2015-12-11 Permalink | Reply
    Tags:   

    jq stuff 

    Waah. In case I *ever* need this again.

    What does it do? It makes a list

    … for each security group which has a name tag. Yeah, right.

     
  • penguin 14:58 on 2015-12-08 Permalink | Reply
    Tags: gnome, usability   

    Shortcut with “ö” (o-umlaut) 

    I want my clipboard history on CTRL-Ö. Don’t ask why.

    Here’s what you can enter in GNOME to get this:

     
  • penguin 10:51 on 2015-12-08 Permalink | Reply
    Tags: ,   

    Rancher IAM role 

    Rancher can create instances on EC2. If you want to define a dedicated IAM user for this, refer to the Amazon docs for the a profile template.

    Unfortunately the first thing you get when using those permissions in rancher is “You are not authorized”. Great. I’ll update this when I know the correct permissions.

    (Source: Rancher docs)

     
  • penguin 13:37 on 2015-12-07 Permalink | Reply
    Tags: , cloudformation   

    VPC with NAT to internet on AWS 

    … and other TLAs.

    Anyways, as far as I remember OpenStack does not need this, so I thought I document it here. I at least was surprised.

    Situation: You want a private network sement in the cloud (in my case an Amazon VPC), and you don’t want all hosts to be accessible from the internet. So you don’t assign public IPs, and you need a router/gateway.

    Amazon creates a network internet gateway, but this thing does not do one thing: NATting. If your host does not have a private IP, it can’t connect to “the internet”.

    Solution: You actually need to instantiate an EC2 instance, which you have to configure to do NAT (which is forwarding and masquerading) with a public IP address. And you have to set routing tables which point to that instance for all networks which should be inaccessible from the internet.

    Thankfully there’s an article providing an example CloudFormation template.

    Really, thanks.

    Configuring the NAT instance is super-easy then. Amazon mentions in its docs that there are special Amazon Linux instances (“These AMIs include the string amzn-ami-vpc-nat in their names […]”) which come with NATting preconfigured. Just instantiate an instance using the appropriate AMI image, and you’re done. No further configuration needed.

     
  • penguin 10:43 on 2015-12-07 Permalink | Reply
    Tags: , cloud, services   

    CI / CD solutions 

    Everyone wants free candy. Or a CI/CD solution, that …

    • auto-deploys container-based servcies
    • auto-updates (roll-forward, roll-back) those services on keypress and “triggers”
    • has one-click-deployment of services.

    My definition of “service” here is “A set of containers working together in a certain way, automatically load balanced where needed”. Example: A n worker nodes, loadbalanced from a web endpoint, and a database container. All deployed at the same time. Including one-click-deployment of environments (“Oh, I’d like to test this revision again, let’s deploy it quickly”…). Note that this is mostly CD (continuous deployment), cause CI is being done for a while now with – mostly – Jenins and other tools.

    What I have found so far that seems to satisfy those requirements:

    And the service-only solutions without a tools tack which you can deploy locally:

    This is kinda it. I would love to evaluate  all those tools, but most of are not really AWS-deploy-friendly, and in the Shippable and Tectonic case they are paid full stack services without local (cloud-owned) deployment anyway. And most are in beta. But the scenery is becoming interesting …

    I will try to post my findings here, as well as the final choice I made for my current client, along with the reasons.

    And for now: Mesosphere and Rancher looks really cool. And I mean “looks” – the UI is just pleasing (which is the most important selection criteria, I know 😉

    Update 2015-12-10: Added Vamp, Kubernetes

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel