Saturday, August 27, 2016

Firebase experience - done

Technically speaking, this issue has been resolved but I am not sure I or the support folks fully understand what went wrong.  Ultimately, as I understand it, the number of free applications on my account was increased and I was then able to transition a project from the original Firebase platform to the new one.

Billing has been and is still enabled on my account so I don't know why the increase of free projects was necessary but it worked.

The tech support person was polite, persistent and ultimately successful.

Now I am trying to recall which of the new features was the original impetus for wanting the upgrade. ;)

Happy coding,
Carl

Wednesday, July 20, 2016

Firebase experience update

While the issue described in the last post is not yet resolved, I have had some very nice email exchanges as well as a conversation via Google Hangouts with a Firebase tech support person.  Apparently despite the fact that I am registered as paying for some Google services, I am bumping into something related to the free limit and tech support needs to work that out with the billing folks.

In the meantime, I will make certain an app or two has billing activated and see what happens.  As I told the tech support person, I believe Firebase is good technology but I am caught in a crack between the legacy and current releases.

I do hope this issue is not existent or made easier for others.

Happy coding (and getting access to technology),
Carl

Monday, July 18, 2016

Firebase experience

I started with Firebase before Google bought the company.  It's definitely a cool technology but as it sometimes happens support is not always great from big companies.

In trying to move an app from the "legacy platform" to the as-of-Google-IO-2016 new platform.  This process seems like it would be simple enough because they built a nice UI which ultimately takes you to an import option.

When I click on the Import button for any of my apps, I get the message I have captured below.


I have had several tech support email exchanges for the past month or so.  They are always polite, sometimes apologizing for my trouble but not necessarily quickly (day, two, or more between emails).

The bottom lines is 1) it's not fixed...yet and 2) I don't think one can rely on such and call it support.

I have a credit card on file with my Google account (I continue to experiment with various Google services) but I have been told this may have something to do with me relying on the free service.

I wrote this entry for a couple of reasons.  First, I would like it solved and I thought perhaps someone else has been down the same road and knows how to get past it.  And secondly, I am tired of answering the same question over and over again and I thought I could simply update this post if/as asked.

Happy coding,
Carl

Sunday, December 27, 2015

Artifactory and Docker

A quick reminder to myself (and anyone else who may miss this) about setting up a Docker repository in JFrog's Artifactory online service.  As of now, this page, has a "Click to expand" link under the "Working with Artifactory Online" section.

The text there explains that there's a special pattern to be followed for naming the repository.  It's this information that I was missing in order to get a repository up and available for use.

Here is an excerpt from those instructions:

First, you need to create a new Docker V2 repository by the name dockerv2-{local/remote/virtual}. 

HTH,
Carl

Friday, November 13, 2015

Opening OpenShift

Docker has occupied a good bit of my free time in recent months.  In addition to Docker and related technology, all things cloud seem to have really exploded in a great way.

On all things cloud, I highly recommend The Cloudcast podcast.  In case you are not aware, this is well produced, first-class production about cloud computing.  So far it seems to be a very well balanced technology mix and it has also reminded me of how competitors in the technology space can learn from and respect one another...when they try.

Lately, OpenShift has, once again, been very much a part of my daily efforts.  Certainly I have used and been impressed with the prior release, but V3 and the move to Docker and Kubernetes under the hood was, in my opinion, an excellent move.  I am working with others on a couple of different OpenShift Enterprise (OSE) installations but the hacker in me learns better when I play with the latest open source bits, as time permits.

If you head over to OpenShift.org it does not take a long to realize there's lots there and doing an installation on your own does not have a bad learning curve, especially given the number of installation options there are.  There is one, however, that I would like to recommend if you want to get up and running quickly on your own development machine, which I am guessing is substantial if doing so is of interest.

Red Hatters Steve Pousty and Brenton Leanhardt co-created the All-in-one Virtual Machine version which you can find here.  If you're not familiar with Vagrant and/or VirtualBox, you'll still do fine with this setup given the nice instructions which are provided.

Work through the examples and you will get an excellent glimpse of OpenShift.  If you're inclined to dig a bit deeper, I suggest SSHing into the VM.  I am no Vagrant expert but if you type "vagrant ssh" (while in the directory from which you completed the installation), you will get to a prompt.  Next, I suggest a "sudo su -" to become root.

A "history" provides a bit of insight into what was involved with the installation.  You might find one or more commands which you'll want to learn more about via the docs.  Of interest to me was the README.md file found here: /data/src/github.com/openshift/origin/examples/sample-app.  It's not that you can't find the same file here on Github, but it was more about learning just what's in this installation (after you have seen it work).  When I first approached this effort, I assumed it was from the Vagrant-OpenShift project but I was corrected and so I decided to dig a bit deeper to learn a bit more about my own similar installation efforts.

Cloud technologies are moving fast right now and if you like the ride, that's a very good thing.

Happy hacking,
Carl


Saturday, July 04, 2015

Docking some

Under the new technologies (at least new to me), comes Docker.  I have been playing with Docker on and off for a good bit now.  I don't think I really got it until JavaOne last October.

I have created a couple of cool use cases since then that I think ultimately will really help our organization.

My most recent find is the Informix image created by IBM which can be found here.  Now that I have a few containers up and running with some real data, I am trying to learn more about best practices for such use cases.

Certainly getting the container running, importing a database, and running it is not difficult but specifically what the automation of all of the above looks like in production is not quite clear to me yet...but I think I am close.

Happy DevOps-ing,
Carl

Saturday, June 13, 2015

REST from Boston

Realizing it's been a long time since I (published) a blog entry, here's what I am up to at the moment...I happen to be in Boston to catch a Red Sox game and I have some down time.



I am coding a REST client for the Domino Access Services which are nicely documented here.  This is one of those project that might take a throw-away effort or two before anything becomes of it but it's one that I think illustrates a couple of other nice projects.

It seems to me that over the years, Spring is one of those technologies that folks love or very strongly dislike.  Personally, I think it's like most solutions: if you apply it when it makes sense, it's good stuff.  Forcing technologies that don't fit a problem is asking for frustration.

If you're coding in Java and need to consume a REST web service, the Spring RestTemplate is worth a look.

Another library I have used several times lately is OWNER  If you Java application utilizes properties, check it out.  This is one of those needs I don't think a lot about but Luigi definitely has...and then some.

BTW, the code, which is still very much a work-in-progress, can be found here.

Happy coding,
Carl