will_hughes

   Location: Sydney, Australia
   Remote: Yes, preferably (I have a quiet home office and 100Mbit+ FTTH internet) 
   Willing to relocate: No
   Technologies:  C#/.NET, Powershell, Windows, Linux (Centos/Ubuntu), Ansible, Octopus Deploy, T-SQL, Redis, HAProxy, IIS, Elasticsearch/ELK, Graphite/Grafana, Zabbix, 
   Résumé/CV: Yes, email me. 
   Email: [email protected] 

I have more than eighteen years of Software Dev experience in the Telecomms, Digital Agency, R&D and Travel industries. Most recently I worked in a small IT Operations ("Devops") team for a high traffic Hotel metasearch company managing their global infrastructure.

I'm looking for another job in the IT Operations space. Remote working would be a plus, but not required.

If you've got a role like this - please reach out.

   Location: Sydney, Australia
   Remote: Yes, preferably (I have a quiet home office and 100Mbit+ FTTH internet) 
   Willing to relocate: Maybe, within AU/NZ - lets talk. 
   Technologies:  C#/.NET, Powershell, Windows, Linux (Centos/Ubuntu), Ansible, Octopus Deploy, T-SQL, Redis, HAProxy, IIS, Elasticsearch/ELK, Graphite/Grafana 
   Résumé/CV: Yes, email me. 
   Email: [email protected] 

I've spent the last ~7 years working for a high traffic hotel metasearch company that was acquired late last year. My title was "Devops Engineer" but if it involved IT, our small team managed it for the whole org. I primarily supported our production infrastructure on a mix of physical and virtual hardware, and cloud services. DNS, CDN, LB, Logging, Metrics, Monitoring, Deployment Orchestration, CI/CD Build Pipeline, and more.

For my next job, I'd like a role involving IT Operations - a mix of backend dev/automation and IT Infrastructure management/monitoring/support.

Does that sound like your company? Give me a shout.

   Location: Sydney, Australia
   Remote: Yes, preferably - at least part of the time (I have a quiet home office and 100Mbit+ FTTH internet) 
   Willing to relocate: Maybe, within AU/NZ - lets talk. 
   Technologies:  C#/.NET, Powershell, Windows, Linux (Centos/Ubuntu), Ansible, Octopus Deploy, T-SQL, Redis, HAProxy, IIS, Elasticsearch/ELK, Graphite/Grafana 
   Résumé/CV: Yes, email me. 
   Email: [email protected] 

I've spent the last ~7 years working for a high traffic hotel metasearch company that was acquired late last year. My title was "Devops Engineer" but if it involved IT, our small team managed it for the whole org. I primarily supported our production infrastructure on a mix of physical and virtual hardware, and cloud services. DNS, CDN, LB, Logging, Metrics, Monitoring, Deployment Orchestration, CI/CD Build Pipeline, and more.

For my next job, I'd like a role involving IT Operations - a mix of backend dev/automation and IT Infrastructure management/monitoring/support. Somewhere that's low BS, and things can get done without endless meetings.

If you're looking for someone to join a team of like minded folks, give me a shout.

> Well clearly I didn't try hard enough

Well, I had the advantage in that I already knew I wasn't touching it on Docker with a ten foot pole, and we use Ansible, so that made my google search pretty obvious.

> Close versions of ES+Kibana not working together

Yep, that's a pain in the arse, and a trap for inexperienced players still.

Also of note is that the latest versions available through the package repository are not the same as the latest supported by the Ansible role. The ansible role will install a specific version of Elastic, you'll have to be careful to take note and synchronise that with the versions of Logstash and Kibana you install. (This is why we're on 6.1.3)

> - maxConcurrentShardRequests not being set on Kibana for some reason (so when I got them talking, a silly query parameter was holding everything up) > - I wasted a ton of time due to some files from a failed installation causing an obtuse error -- I think it was a NoShardAvailableActionException

yeah, can't really help with either of these two - I already had a working ELK1.7 install, so for us it was pretty much a case of stand things up, and perform some modifications to templates/queries/etc, and off we went.

The one thing I miss about working for a major national telco was access to the internal newsgroups where you'd get deep discussions triggered by someone's random question on things.

Probably because they support older SSL/TLS versions and/or cryptographic ciphers.

> will just report you to the cops if they see sleight-of-hand

Why? Just add it to the order.

Wrong thread?

Also, it may be true where you are, but it's not universally true. I know the cycle and timing of the lights near my home, and I keep getting frustrated by people who don't press the button and now I need to press it, and wait an extra cycle.

> I think they should only retaliate on US officials (elected and who work for DHS). Ask them to reveal passwords to national secrets when they enter the country, then detain them for hours when they refuse.

Unfortunately I don't think this will do what you expect - they'll probably happily hand over their password.

> what's the problem with the HTTP-01 challenge?

Nothing, yet.

But who's to say that another similar bug won't be found in common shared-hosting platforms that forces LE to turn that challenge off too?

This is already covered in the book. The water ice on Ceres had already been used up in the colonisation efforts of Earth and then later: Mars.

> Nothing says I control the domain like the ability to add and remove data from the authoritative DNS servers for the domain label (and children thereof) in question.

Unfortunately this makes life difficult for us.

We run a whitelabelled platform with tens of thousands of users - it's hard enough to get many people to understand setting a CNAME record (vs just setting an A record). Requiring them to update a TXT record once would be a big enough challenge, but doing it every 30-90 days is never going to happen. The smaller customers would probably be happy with us hosting their DNS, but we're not going to do that - the larger ones wouldn't.

TLS-SNI being gone and DNS being unworkable means we're left with HTTP only.

You're going to find it a hard road to convince anyone that ISPs shouldn't be able to perform standard network management activities on their network.

It's also extremely unhelpful to bring it up in the context of NN.