byobu incorrectly assumes EC2

[Ben Howard]

Byobu incorrectly assumes that it is running on EC2 and calculates the incorrect usage fees on OpenStack installations. For example on HP's Beta.

Example Meta-data:
availability-zone: nova
block-device-mapping: ami
root
ephemeral0
instance-action: none
instance-id: i-00008e05
instance-type: standard.2xlarge
local-hostname: server-36357

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: byobu 4.37-0ubuntu1
ProcVersionSignature: User Name 3.0.0-12.20-virtual 3.0.4
Uname: Linux 3.0.0-12-virtual x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Thu Feb 9 23:58:57 2012
Ec2AMI: ami-000000e5
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: standard.2xlarge
Ec2Kernel: aki-000000e4
Ec2Ramdisk: unavailable
PackageArchitecture: all
ProcEnviron:
 LC_CTYPE=en_US.UTF-8
 LC_COLLATE=en_US.UTF-8
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
ScreenRC:

SourcePackage: byobu
UpgradeStatus: No upgrade log present (probably fresh install)

[Dustin Kirkland  (kirkland)]

Thanks, Ben!

What do you recommend as the correct behavior here for Byobu?

Should it not print anything, since HP's OpenStack Beta cloud is free?

Should it use a different cost structure?

Note that there's both an ec2_cost and an rcs_cost (rackspace cloud)
status item, that use independent cost structures and algorithms.

What do you think Byobu should do?

[Ben Howard (darkmuggle-deactivatedaccount)]

Hi Dustin....my gut is that absent a cost structure or an identification of the cloud it should display nothing. I would rather not have the information than incorrect information. As more vendors (i.e. AT&T) pick up Byobu, I can see this becoming a frequent issue.

[Dustin Kirkland  (kirkland)]

So I really, really *want* to see my ec2 cost, when I am running in EC2 and I know my instance type.

If I don't know my instance type, then it will default to showing nothing, unless the user explicitly configures that they want to see the estimation of what this instance *would* have cost in EC2 (which is still a valid use of the status item).

[Dustin Kirkland  (kirkland)]

Committed revision 1918. Will be in byobu-5.13.

[Launchpad Janitor (janitor)]

This bug was fixed in the package byobu - 5.13-0ubuntu1

---------------
byobu (5.13-0ubuntu1) precise; urgency=low

  * usr/lib/byobu/include/mondrian:
    - simply speed up using perl
  * usr/bin/byobu: LP: #937175
    - check tput for 256 color support before defaulting to that in tmux mode
  * usr/lib/byobu/disk_io: LP: #934893, #936393
    - initialize the x1 value correctly
  * usr/lib/byobu/ec2_cost, usr/share/byobu/status/statusrc,
    usr/share/man/man1/byobu.1: LP: #929907
    - disable the ec2_cost plugin if not running in EC2,
      allow override with EC2_ESTIMATE=1 in ~/.byobu/statusrc
  * usr/lib/byobu/include/shutil: LP: #930656
    - support network interface detection on Mac OSX
    - untested by me, but sort of suggested by a user
  * etc/byobu/backend, usr/lib/byobu/include/common,
    usr/lib/byobu/include/constants: LP: #937174
    - fix upgrades while within a running byobu-screen session
 -- Dustin Kirkland <email address hidden> Thu, 16 Feb 2012 23:58:36 -0600